The ACP-620 Managing Jira Projects for Cloud Exam validates your ability to plan, configure, and oversee Jira Cloud projects from setup through execution and reporting. This certification is designed for project managers, team leads, and Jira administrators who need to demonstrate practical expertise in the Atlassian Certified Professional program. This page provides a clear study roadmap covering all exam domains, question formats, and actionable preparation strategies. Whether you're new to Jira Cloud or strengthening existing skills, you'll find guidance aligned to real-world project scenarios.
Use this topic map to guide your study for Atlassian ACP-620 (Managing Jira Projects for Cloud Exam) within the Atlassian Certified Professional path.
The ACP-620 exam uses multiple question types to assess both conceptual knowledge and applied decision-making in Jira Cloud project management.
Questions increase in complexity and reward candidates who connect topics across the full project lifecycle, from creation through delivery and analysis.
Effective preparation requires mapping each topic to focused study blocks and practicing with realistic scenarios. Allocate 4-6 weeks to cover all domains thoroughly, with time for hands-on exploration and review cycles. Structure your study around the five core topics, building from foundational setup knowledge to advanced automation and reporting use cases.
Explore other Atlassian certifications: view all Atlassian exams.
Strengthen your preparation with up-to-date resources from validexamdumps.com. These materials align to ACP-620 and cover practical scenarios with clear explanations.
Visit the exam page to download the PDF, Online Practice Test, or get a Bundle Discount offer for both formats: Managing Jira Projects for Cloud Exam.
Board Configuration and Managing Projects typically account for a larger portion of the exam, since these directly impact how teams work day-to-day. However, all five domains are tested, and automation and reporting questions often appear in scenario-based items that require connecting multiple concepts. Focus on depth across all topics rather than skipping any single area.
When you create a project, you establish the foundation (template, permissions, workflow). Board Configuration then shapes how the team visualizes and moves work. Automation rules then enforce consistency by triggering actions based on board transitions and issue events. Understanding this chain helps you see how each topic supports the others and why mastering all three is essential for effective project management.
Practical experience is valuable, especially with Board Configuration and Automation where you need to understand feature behavior and side effects. If you have limited hands-on time, prioritize creating a test project, configuring a Kanban board, and building one or two automation rules. This foundation makes scenario-based questions much easier to reason through.
Misunderstanding permission schemes and their impact on user visibility is a frequent error. Another common mistake is confusing board-level filters with project-level workflow rules. Candidates also sometimes choose automation rules that work but are overly complex or inefficient. Review the "why" behind each answer, not just the correct option, to avoid these pitfalls.
Review any topics where you scored below 80% on practice tests. Take a full-length timed mock to build pacing and identify any remaining knowledge gaps. Spend the final 2-3 days reviewing Reporting and Automation, since these topics often appear in multi-step scenario questions that require careful analysis. Get adequate sleep the night before the exam to ensure sharp decision-making.
Your team wants to measure their performance based on the number of issues completed in each sprint.
Currently, they are measured based on the number of story points completed instead.
Which board configuration needs to be changed?
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 team requests that you configure their Kanban board in such a way that they can:
see just particular subsets of issues based on values in a radio button field
see all issues grouped by the epic they belong to
distinguish cards visually based on their priority
Select three board configurations that when combined together, will satisfy these requirements. (Choose three.)
Card colors by priority: Visually distinguishes issue cards on the board based on their priority.
Swimlanes by epic: Groups all issues under their respective epics, helping the team see work organized by feature or theme.
Quick filters based on radio button field: Allows team members to filter and view specific subsets of issues depending on the selected radio button field value.
Your project is configured as shown.
An issue is created with all three components selected: Hardware, Software, and Infrastructure. The assignee is set to Automatic. Who will be automatically assigned to the issue?
When multiple components are selected on issue creation, Jira cannot determine a single default assignee if each component has a different assignee rule. In this case:
Hardware Component lead (Vincent Choy)
Software Project default (Alana Grant)
Infrastructure Unassigned
Since the assignee logic conflicts, Jira defaults to Unassigned to avoid ambiguity.
You need to write a JQL query showing:
issues where the Priority was High in the past and may or may not still be High
Identify two JQL statements that will return the correct results. (Choose two.)
priority changed to High before now(): This returns issues where the priority was set to High at any point in the past, regardless of its current value.
priority was High: This returns issues that had High priority at some point, whether or not they still have it. Both satisfy the requirement to show issues where the priority was High in the past and may or may not still be.
You need to configure automatic issue assignment in a company-managed project.
Assignment depends on a value selected by users during issue creation.
Users should be able to select only one value.
Identify two elements that can be configured together to meet this need. (Choose two.)
Radio Buttons custom field: Ensures users select only one value during issue creation, which can then drive assignment logic.
Automation rule: Can be configured to automatically assign issues based on the selected value in the custom field, enabling dynamic and rule-based assignments.
