ACP-610 Managing Jira Projects for Data Center and Server Certification Questions and Answers

As a project administrator of DEV, you can update some project settings such as project shortcuts, description, name, and versions. However, you cannot update the notification scheme or the key of the project, as these are global settings that require Jira administratorpermissions. Therefore, the correct answer is A and C. References: Managing project permissions, Managing project notifications, Changing the project key

A select list (single choice) field meets the requirements because it allows different options in different projects, allows options to be disabled where necessary, allows only a single value, and allows a default value to be configured. A select list (single choice) field is a custom field that lets the user select one option from a list of predefined values. The values can be different for each project and can be enabled or disabled as needed. The field can also have a default value that is automatically selected when creating an issue12 References:

• 1: What are custom fields? | Jira Software Cloud | Atlassian Support
• 2: Configuring a custom field | Jira Software Cloud | Atlassian Support

The label field meets the team’s requirements for flagging issues using a category. Labels are a type of custom field that allow users to add one or more descriptive tags to issues. Users can add new labels on the fly, and select existing labels from a dropdown menu. Labels can be re-used across all projects, and can be searched and filtered easily. A text field does not allow multiple values or a dropdown menu. A component does not allow multiple values or adding new values by any user. A user picker does not allow multiple values or adding new values byany user. Checkboxes do not allow adding new values by any user. References: [Adding, removing and searching for labels], [Managing Jira Projects Data Center and Server: Certification Bundle]

 Based on the current configuration, the assignee field will show Mac Taylor after creating the test issue. This is because the Macbook 13" component has Mac Taylor as the component lead and the component/s field has been configured to override the project’s default assignee when using a certain component. Therefore, when creating an issue with the Macbook 13" component, the assignee field will automatically be set to Mac Taylor, regardless of the default assignee of the project or the value of the assignee field before creating the issue34 References:

• 3: What are components? | Jira Software Cloud | Atlassian Support
• 4: How to enable and edit component/s , affects Version/s and fix version …

The Cumulative Flow Diagram is the report that provides the information that the head of customer service wants. The Cumulative Flow Diagram is a tool that visualizes the quantity and distribution of work items along different stages of a process. The report shows how many work items are in each stage at any given time, and how they flow from one stage to another. The report can help identify potential bottlenecks in the support workflow by showing where work items accumulate or stagnate over time. For example, if the report shows a sudden increase or a wide band of work items in the “Waiting for Customer” stage, it may indicate that the customers are not responding quickly enough or that the support team is not following up effectively. The report can also help monitor the overall progress and performance of the support teams by showing the total number of work items created, resolved, and remaining over time. References: Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

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. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Advanced searching - functions reference | Jira Software Cloud]

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

A Sprint Report is also the best report to meet this need. As explained above, a Sprint Report shows a list of the incomplete issues in the sprint and allows you to quickly view that list in the Issue Navigator. A Sprint Report can help you investigate why your team failed to meet their last sprint commitment by showing you how many issues were added or removed during the sprint, how many issues were completed or not completed, and how much work was carried over to the next sprint. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

A Sprint Report is the best report to provide a list of all issues included in a particular sprint. A Sprint Report shows the scope, status, and completion date of each sprint. It also displays a breakdown of the completed, incomplete, and added issues in the sprint. The release manager can easily view the list of incomplete issues in the Issue Navigator by clicking on the View in Issue Navigator link at the bottom of the report. A Sprint Report also helps to track the team’s performance and identify any scope changes during the sprint. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

The statement that is definitely true is that bugs can be dragged from “In Progress” to “In Test” on this board. This is because the board configuration shown in the image has two columns: “In Progress” and “Done”. The “In Progress” column has three statuses mapped to it: “To Do”, “InProgress”, and “In Test”. The “Done” column has one status mapped to it: “Done”. Therefore, issues can be moved from one status to another within the same column by dragging them on the board. However, issues cannot be moved from one column to another by dragging them on the board, as this would require a workflow transition that is not available in a simplified workflow. A simplified workflow is a default workflow that allows any user with the Edit Issues permission to add or remove statuses on the fly. To move an issue from one column to another, you need to use the workflow button on the issue detail view and select a transition that matches the status of the destination column. References: Configuring columns, Using a simplified workflow

The epic completion date is hard to predict because the team adds new stories throughout the epic. This means that the scope of the epic is not fixed and can change over time. The Epic Report shows the progress of an epic by comparing the estimated amount of work to the completed work. The report also shows a projected completion date based on the team’saverage velocity. However, if the team keeps adding new stories to the epic, the estimated amount of work will increase and the projected completion date will be pushed further. This makes it difficult to plan and deliver the epic within a certain timeframe. References: Managing Jira Projects Data Center and Server: Certification Bundle, Epic Report

The correct JQL query to find all issues that were in the Closed status at some point in their lifecycle is: status WAS Closed. This query uses the WAS operator to check the previous values of the status field. The other options are incorrect because they either use invalid syntax, such as CHANGED FROM or -, or they do not capture all the issues that were ever closed, such as status = Closed or status CHANGED TO Open. For more information on JQL syntax and operators, see Advanced searching - operators reference and Advanced searching - fields reference. References: Advanced searching - operators reference, Advanced searching - fields reference

If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D. References: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]

• Savresh needs Assignable User permission. This permission determines which users can be assigned to issues in a project1. If Savresh does not have this permission, they will not be able to re-assign issues to themselves, even if they can create and assign issues to others.
• Testers need Assign Issues permission. This permission determines which users can assign issues to other users or to themselves1. If the Testers group does nothave this permission, they will not be able to re-assign issues to anyone, including Savresh.

The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how toconfigure fields in Jira, see Configuring fields and screens. References: Configuring fields and screens