Pass the ATLASSIAN Jira Project Administrator ACP-610 Questions and answers with CertsForce

 The best course of action is to restore the project, then the sub-tasks. This is because sub-tasks cannot exist without their parent issues, and parent issues cannot exist without their project. Therefore, restoring the project first will ensure that the parent issues are also restored, and then restoring the sub-tasks will re-attach them to their parent issues. Restoring the parent issues only will not restore the sub-tasks, as they are still archived. Restoring the project only will not restore the sub-tasks, as they need to be restored separately. Restoring the parent issues, then the sub-tasks will not work, as the parent issues cannot be restored without their project. Restoring the project, then the parent issues is unnecessary, as the parent issues are already restored with the project. References: [Restoring an archived issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

The gadget that meets Kim’s need is the Issue Statistics gadget. This gadget displays the collection of issues returned from a filter, broken down by a field. Kim can configure the gadget to use her project as the filter, and the issue type as the field. The gadget will then show the following information for issues in her project:

the total count of all issues

the total count of each issue type

the distribution of each issue type as a percentage

a graphical chart display of that percentage

The other gadgets are not suitable because:

The Heat Map gadget displays issues from a project or filter, grouped by a statistic type, in a heat map format. Issues can be grouped by any statistic type (e.g. Status, Priority, Assignee, etc). However, this gadget does not show the total count of all issues, nor the distribution of each issue type as a percentage.

The Two Dimensional Filter Statistics gadget displays issues from a filter in a table format, where each cell shows the number of issues for a given combination of two statistics types (e.g. Status vs Priority, Assignee vs Issue Type, etc). This gadget does not show the total count of all issues, nor a graphical chart display of that percentage.

The Filter Results gadget displays the results of an issue filter on the dashboard. This gadget does not show any summary or breakdown of the issues by any field, nor a graphical chart display of that percentage.

The Issues in Progress gadget displays all issues that are in progress and assigned to the user viewing the dashboard. This gadget does not show any information about other issues or issue types in the project, nor a graphical chart display of that percentage.

References: Use dashboard gadgets, Gadgets for Jira applications

An epic burndown chart shows the progress towards completing an epic over time. It is useful for tracking how much work is left to be done and predicting when it will be completed. The epic burndown chart is based on the estimation statistic that is configured for the board (either story points or issue count) and shows the total amount of work remaining in the epic at the end of each sprint. You can use this chart to estimate how many additional sprints will be needed to complete an epic. References: : https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-epic-burndown-chart/

Jira attachments are files that users can attach to issues to share information with their team. Users can search for issues that contain attachments by using the attachments field in the advanced search. For example, attachments is not EMPTY will return all issues that have at least one attachment. Therefore, option A is true.

A custom field is a field that is not part of the default set of Jira system fields. Creating a new custom field requires Jira administration permissions, so Max cannot perform action 1. However, adding an existing custom field to a transition screen does not require Jira administration permissions, as long as the screen is not shared with other projects or issue types. Therefore, Max can perform action 2 if he has the “Administer Projects” permission and the screen meets the prerequisites for editing. References: : https://support.atlassian.com/jira-software-cloud/docs/what-are-custom-fields/ https://support.atlassian.com/jira-software-cloud/docs/configure-screens/

Bob needs security level access to see all the issues in the scrum project. Security levels are a way of restricting the visibility of certain issues within a project to specific users or groups. If Bob does not have the appropriate security level for some issues, he will not be able to see them. Browse Projects permission alone is not enough to see all the issues in a project that hassecurity levels configured. Project permission, global permission, and board access are not related to issue visibility within a project. References: Configuring issue-level security, Managing Jira Projects Data Center and Server: Certification Bundle

Two project roles that must be granted to view code commits in the DEV project are:

Developers

Administrators

According to the image you sent, the View Development Tools permission determines which users can see development information from tools such as Bitbucket, GitHub, FishEye, and Crucible. This permission is granted to the Project role (Developers) and the Project role (Administrators) in the DEV permission scheme. Therefore, users who are assigned to these roles will be able to view code commits in the DEV project.

The other options are not correct because:

Users do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.

Sprinters do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.

Managers do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.