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

The solution that will meet the team’s requirements of using agile boards with minimal disruption to their current configuration is to use a Kanban board for tasks and a Scrum board for features in the current project. This way, they can use different agile methodologies for different issue types without creating a new project or changing their existing configuration. They can use a Kanban board for tasks to handle them based on priority and rank and release them incrementally as needed. They can use a Scrum board for features to develop them during three week iterations with sprints and backlogs. The other solutions are either not feasible or not optimal for their needs. Therefore, the correct answer is E.  References : [Creating a board], [Using a Scrum board] , [Using a Kanban board]

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.

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’s average 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 statement that is definitely true is that changes to the rank of integration issues on Jo’s board are reflected on Sam’s board. This is because ranking is a global attribute that affects how issues are ordered across projects and boards based on their relative priority. When Jo updates his Scrum board’s saved filter to include integration issues from Sam’s project, he can rank them along with his own issues on his board. These changes will also affect how these issues are ranked on Sam’s board, as they share the same rank field value. The other statements are not necessarily true or false, as they depend on other factors such as permissions, workflow configurations, or board settings. Therefore, the correct answer is B.  References : [Ranking an issue], [Configuring filters]

A project administrator can remove watchers from project notifications, if they have the Manage Watchers permission. This is a task that does not require Jira administrator access, and can be done by the project administrator from the issue view. Removing a priority value used by the project, updating permissions for a project user, and limiting who can bulk edit project issues are all tasks that require Jira administrator access, and cannot be done by the project administrator.  References:   Managing watchers ,  Managing Jira Projects Data Center and Server: Certification Bundle

The board filter query that meets these requirements is (project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic). This query will show all issue types from project BERT except sub-tasks, as well as only epics from project ERNIE. It will not show issues from any other projects, as it uses the OR operator to combine two conditions that specify the project names. The other queries do not meet all the requirements, as they either include sub-tasks from project BERT, exclude epics from project ERNIE, or show issues from other projects.  References :  Configuring filters , Advanced searching - fields reference

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]

Savresh needs Assignable User permission.  This permission determines which users can be assigned to issues in a project 1 . 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 themselves 1 . If the Testers group does not have this permission, they will not be able to re-assign issues to anyone, including Savresh.

The issue will appear in the  Expedite  swimlane, because it matches the query  priority = Blocker . Swimlanes are used to group issues on the board based on a common attribute, such as assignee, epic, or a custom query. The board’s swimlane configuration shows that the first swimlane is Expedite, which has the query  priority = Blocker . This means that any issue with a blocker priority will be placed in this swimlane, regardless of its other attributes. The other swimlanes have different queries that do not match the issue’s attributes, such as type, labels, or reporter. Therefore, the issue will not appear in those swimlanes. The last swimlane is Everything Else, which is the default swimlane for any issue that does not match any of the previous queries. However, since the issue matches the Expedite query, it will not fall into this swimlane either. Hence, the correct answer is B.  References:  [Configuring swimlanes], [Using swimlanes]

The correct JQL query to find issues reported by either Paul or Tessa that are still unassigned is: Reporter IN (Paul, Tessa) AND Assignee IS EMPTY. This query uses the IN operator to specify a list of values for the Reporter field, and the IS EMPTY operator to check if the Assignee field has no value. The other options are incorrect because they use invalid syntax or operators, such as “-”, NULL, or Unassigned. For more information on JQL syntax and operators, see  JQL operators  and  Use advanced search with Jira Query Language (JQL) .  References:   JQL operators ,  Use advanced search with Jira Query Language (JQL)

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”, “In Progress”, 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

This JQL query is always correct because it uses the  duedate  field, which is a date picker that stores a date value without a time component, and the  startOfDay()  function, which returns the start of the current day (i.e., midnight). This query will return all issues that have a due date before today and are assigned to either Adam or Eve. The other queries are either incorrect or unreliable because they use different fields or functions that may not work as expected. For example, the  due  field is a date time picker that stores both a date and a time value, and the  currentLogin()  function returns the date and time of the current user’s last login, which may vary depending on the user and their timezone.  References:  : https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Advancedsearchingfieldsreference-DuedateDuedate https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-startOfDaystartOfDay

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]

The team can use the Release link to remove issues as needed from the Done column. This will create a version in the project that contains all the issues that were removed, and the team can use the version report to see the details of each clean-up. Excluding issues in Done status from the board filter or via a sub-filter will not remove them from the Done column, but only hide them from view. Excluding issues where Resolution != EMPTY from the board filter will also hide issues from other columns that have a resolution set, which is not desired.  References:  [Releasing a version], [Managing Jira Projects Data Center and Server: Certification Bundle]

The Velocity Chart is the best report to compare work committed and work completed in sprints over time. It shows the average amount of work that a team can complete in a sprint, based on the historical data of previous sprints. It also shows how much work was planned and how much was actually completed in each sprint. By looking at the Velocity Chart, a team can see if they are overestimating or underestimating their capacity, and adjust their planning accordingly. Therefore, option E is correct.  References:   Velocity Chart ,  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]

When you move an epic between projects that share an issue type scheme, all standard issues in the epic are moved along with it. This means that any issue type that is not a sub-task or an epic will be moved to the new project. Sub-task issues in the epic will not be moved unless their parent issues are also in the epic. Story issues in the epic will be moved only if they are standard issue types, not sub-tasks. Issues linked to the epic through issue links will not be moved as they are not part of the epic hierarchy. Therefore, the correct answer is A.  References :  Moving an issue ,  Working with epics

The two actions that are reflected as scope change are dragging an estimated story from the backlog to the sprint and modifying the estimate value on a committed story. Scope change is a measure of how much work was added or removed from a sprint after it started. It is calculated by comparing the total story points committed at the start of the sprint and the total story points completed at the end of the sprint. If you add or remove issues from a sprint, or change their estimates, you are changing the scope of the sprint. The other actions mentioned in the question do not affect the scope of the sprint, as they do not change the amount of work planned or done in the sprint.  References : Viewing the Velocity Chart, Scope change