Free ACP-620 Practice Test

A company-managed Scrum board can be configured to pull issues from multiple projects, enabling cross-team planning and coordination. This makes it ideal for multiple development teams working across several projects and planning their iterations in a single board.

A Kanban board without backlog displays all issues on a single view and supports a continuous workflow without start and stop dates. This setup is ideal for teams using a continuous delivery process, allowing issues to move freely across the entire workflow.

The Estimation Statistic setting on the Scrum board controls whether performance is measured by story points, issue count, or other metrics. To measure performance based on the number of issues completed instead of story points, you need to change this setting to Issue Count.

The Resolution Time gadget displays the average number of days that resolved issues were open over a specified period. It provides insights into how long issues took to resolve, aligning exactly with the team's requirement.

The Time tracking field is required to allow users to enter the number of days (or time) spent and the remaining estimate on issues. Adding this field to the Design issue type enables tracking of effort in terms of logged and remaining time.

Project administrators can use automation rules to send customized emails during workflow transitions. This allows targeted communication to various groups without needing global admin rights, which are required for modifying notification schemes or installing apps.

The Labels field type allows users to select multiple values and add new ones on the fly if they don't already exist. This meets the team's need to flag issues with one or more colors and dynamically add new color options.

Link issue: Allows users to link to another Jira issue, providing contextual connections between related work items. Link Confluence page: Enables linking a Confluence knowledgebase article directly to the Jira issue. Add web link: Lets users attach external URLs, such as industry white papers, to the issue for easy reference.

In team-managed projects, only the Administrator role has full access to all permissions, including advanced actions like managing sprints and removing watchers. While the Member and Custom roles may cover some actions, only the Administrator role definitely grants all the listed capabilities.

Some of the issues are hidden by issue security levels: Amanda may not have permission to view issues restricted by security levels, causing her to see fewer results. She does not meet the currentUser() criteria in the saved filter: If the saved filter uses currentUser() in its JQL and Amanda doesn’t match its logic, the results shown to her will differ from those seen by others.