Atlassian ACP-610 Exam Dumps

The report that can provide an instant progress overview of all fix versions across all projects is the Pie Chart Report. This report allows you to create a pie chart based on any statistic type, such as Fix Version, Project, Issue Type, etc. You can use this report to compare the relative proportions of issues in different fix versions across different projects. For example, you can create a pie chart based on the Fix Version statistic type, and select all the projects that you are responsible for. This will show you how many issues are assigned to each fix version in each project, and what percentage they represent of the total issues. You can also filter the issues by status, priority, assignee, or any other criteria. This report can help you monitor the progress of your releases and identify any potential risks or delays. To generate a Pie Chart Report, follow these steps1:

Navigate to the project that you want to report on.

From the project sidebar, select Reports.

Select Pie Chart Report from the list of reports.

Select the statistic type that you want to base your pie chart on. In this case, select Fix Version.

Select the projects that you want to include in your report. You can select multiple projects by holding down the Ctrl key (Windows) or Command key (Mac) while clicking on the project names.

Optionally, select a filter to narrow down the issues that you want to include in your report. You can use an existing filter or create a new one.

Click View to generate the report.

You can also access the Pie Chart Report from your dashboard by adding the Jira Chart gadget2. This gadget allows you to display any Jira report on your dashboard. To add the Jira Chart gadget to your dashboard, follow these steps2:

Navigate to your dashboard and click Add gadget.

Search for Jira Chart and click Add gadget.

Configure the gadget settings as follows:

Select Pie Chart as the chart type.

Select the project or filter that you want to use as the data source.

Select Fix Version as the statistic type.

Optionally, select a series to further break down the data by another statistic type, such as Status or Priority.

Click Save.

You can also edit or delete the gadget at any time by clicking on the menu icon at the top right corner of the gadget.

The best way to meet the team's requirement is to use the currentUser() JQL function in the filter. This function returns the current user who is viewing the gadget, and can be used to filter issues by assignee. For example, if the filter is ''project = ABC and assignee = currentUser()'', then each person who views the gadget will see counts of only their assigned issues by status. This way, you do not need to reconfigure the dashboard viewers or modify the Assignable User permission, which are global settings that affect all users. You also do not need to replace it with the ''Assigned to Me'' gadget, which does not show counts by status. Configuring the ''Who can view this filter'' setting does not affect the results of the filter, but only its visibility.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, [Advanced searching - functions reference | Jira Software Cloud]

The Version Report and the Sprint Health Gadget are two gadgets that can show the information that the product owner needs. The Version Report shows the progress of a version by comparing the estimated amount of work to the completed work. The report also shows a projected release date based on the team's average velocity. The product owner can use this report to monitor the overall progress of the next release and determine if it will ship on time. The Sprint Health Gadget shows a snapshot of key sprint information such as time elapsed, percentage of scope change, sprint goal, and team members' availability. The product owner can use this gadget to see how each scrum team is performing in their current sprint and identify any issues or risks.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, Version Report, Sprint Health Gadget

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.