Correct Answer: AE

The two functions that are needed to use in the JQL query to find all issues that were not completed in some past sprint, and that are now part of an active sprint are closedSprints() and openSprints(). The closedSprints() function returns all issues that are assigned to a completed sprint. The openSprints() function returns all issues thatare assigned to an incomplete sprint. By combining these two functions with the NOT operator, we can filter out the issues that belong to both a completed sprint and an incomplete sprint, and only get the issues that were not completed in some past sprint, and that are now part of an active sprint. For example, the JQL query could be: project = XYZ AND issuekey NOT IN (closedSprints() AND openSprints()) This query will return all issues in project XYZ that are not in both a closed sprint and an open sprint, meaning they are either in a closed sprint only or an open sprint only. Since we are looking for issues that are now part of an active sprint, we can assume they are in an open sprint only. References: Advanced search reference - JQL functions, Modifying closedSprints() to return previous two Sprints, JQL

-of what closedSprints() does

Correct Answer: CE

When a project is created with a shared configuration, it inherits the configurations of an existing project. This includes the workflow, issue types, screens, fields, permissions, notifications, and schemes associated with them. However, the component lead assignments and versions are specific to each project and are not shared. Therefore, the correct answer is C and E. References: Creating a project, Configuring projects

Correct Answer: B

A possible reason why Sam can only see some of the issues on the project's Kanban board but sees all of them in the issue search is that the column mapping of the board does not include all the statuses of the different workflows used by the issue types. Column mapping determines which statuses are mapped to which columns on a board, and only issues with mapped statuses are displayed on the board. If an issue type has a workflow with a status that is not mapped to any column, then it will not appear on the board. Board permissions, issue-level security, and workflow conditions do not affect the visibility of issues on a board, as they apply to both the board and the issue search. Therefore, the correct answer is B. References: [Configuring columns], [Configuring workflows]

Correct Answer: C

Epics are moved automatically but epic links are lost when stories are moved to another project using a bulk operation. This is because epics are a type of issue, and issues can be moved across projects. However, epic links are a type of issue link, and issue links cannot be moved across projects. Therefore, the stories will lose their epic links after the move, and the epics will remain in the original project. References: [Moving multiple issues], [Managing Jira Projects Data Center and Server: Certification Bundle]

Correct Answer: A

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/

Correct Answer: D

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]

Correct Answer: C

Jon needs Move Issues and Create Issues permissions to move an issue from project A to project B. Move Issues permission allows him to initiate the move operation, while Create Issues permission allows him to create the issue in the destination project. Transition Issues permission is not relevant for moving issues, as it only affects workflow transitions. Administer Projects permission is not required for moving issues, unless the issue type or workflow needs to be changed during the move. Assign Issues permission is not required for moving issues, unless the assignee needs to be changed during the move. References: [Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

Correct Answer: B

Correct Answer: AC

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. References: Managing Jira Projects Data Center and Server: Certification Bundle, Version Report, Sprint Health Gadget

Correct Answer: C

If Quang can transition issues from Resolved to Done using the workflow button on issues in his project, but cannot drag them from Resolved to Done on the project's Kanban board, a possible reason is that the statuses are mapped to the same column. The columns on a Kanban board represent the stages of work in a project. Each column can have one or more statuses mapped to it. To move an issue from one column to another, you need to drag and drop it to a column that has a different status mapped to it. If the statuses are mapped to the same column, you cannot move the issue by dragging it on the board, but you can still use the workflow button to change its status. References: Configuring columns, Moving an issue