Atlassian Certifications: Current Jira Cloud Credentials and Legacy ACP Exams

Atlassian certification has been shifting decisively toward cloud administration and role-based credentials. That creates an important distinction between current certifications and older ACP exam codes that were built for Jira Server or Data Center. Candidates should use the current Atlassian Learning certification catalog as the authority, while older exam versions can still provide historical context when the page clearly identifies them as legacy.

Jira Administration for Cloud is a core current credential

The current Jira Administration for Cloud certification validates the ability to configure and manage Jira Cloud for development and business teams. Candidates are expected to understand global configuration, permissions, schemes, work types, fields, screens, workflows, notifications, and integrations. The certification is role-based: it is intended for people who administer Jira environments, not merely users who create and update work items.

Preparation should include solving configuration problems rather than memorizing interface locations. An administrator needs to reason about inheritance, shared schemes, permission boundaries, workflow behavior, and the consequences of changes across projects. Cloud administration also increasingly includes organization-level governance and coordination with identity and security teams.

Managing Jira Service Projects for Cloud remains directly relevant

The credential lineage includes ACP-420, the Managing Jira Service Projects for Cloud exam. It aligns with service-project administration: request types, queues, SLAs, portals, automation, forms, customer permissions, and the way service teams structure work in Jira Service Management.

That specialization is useful because service management requires a different mental model from software-project administration. Candidates need to understand customer-facing intake, triage, fulfillment, escalation, knowledge, and service-level behavior. The surrounding principles of service management matter more than simply learning product screens.

ACP-620 is active but approaching retirement

ACP-620 maps to Managing Jira Projects for Cloud. Atlassian has announced that this certification will retire in January 2027, with selected content moving into an updated Jira Administration for Cloud exam. That makes status wording especially important in 2026: ACP-620 is still a current transition exam, but candidates planning a longer study timeline should consider whether the successor structure better matches their goals.

The exam's project-administration focus includes project configuration, issue types, workflows, boards, permissions, and team-specific behavior. Concepts such as Scrum and Kanban are relevant because Jira projects often encode the operational rules of an agile team. A practical overview of Scrum artifacts helps candidates connect Jira objects to the underlying work-management model.

ACP-100 and ACP-600 belong to the older era

Older Atlassian exams include ACP-100, a Jira Administrator exam, and ACP-600, Project Administration in Jira Server. These are historical references rather than the current certification path. Atlassian has moved its certification catalog toward cloud products, and Data Center-related certifications have been retired as part of that transition.

Legacy exams are still useful when a reader needs to understand older terminology or is maintaining long-lived deployments, but they should never be described as current prerequisites. Modern candidates should focus on Jira Cloud administration and the live role-based credentials shown in Atlassian Learning.

Cloud administration requires governance as well as configuration

As Jira estates grow, administrators need to think about maintainability. Too many bespoke workflows, fields, statuses, and schemes make the environment harder to govern. Good administrators reuse configurations where appropriate, document exceptions, manage permissions deliberately, and understand how local project choices affect reporting and cross-team work.

Agile concepts matter because Jira configuration is often used to implement team process. The broader discussion of agile and Scrum in practice is relevant when evaluating whether a workflow supports the team's actual operating model or simply reproduces a generic template.

Automation and integration are increasingly important

Jira Cloud administration now extends into automation rules, marketplace apps, APIs, identity integrations, and connections with development or collaboration tools. Administrators should know when to automate repetitive transitions or notifications, how to avoid rule loops and unnecessary complexity, and how to diagnose failures using audit information.

They also need to think about data boundaries. An integration can expose issue content, user data, or operational metadata to another system, so app permissions and organizational governance should be part of the configuration conversation. Cloud administration is therefore both a productivity discipline and a control function.

Confluence and the wider Atlassian system of work

Even when the exam is Jira-centered, administrators benefit from understanding how Jira, Confluence, service management, development tooling, and newer Atlassian platform capabilities fit together. Teams often use Confluence for knowledge and decision records while Jira tracks execution. Service teams may connect Jira Service Management with knowledge bases and automation. Organization administrators manage identity, access, and policy across the broader platform.

That wider view helps candidates avoid treating each certification as a product silo. Atlassian's credential strategy increasingly validates roles within a connected cloud environment.

How to prepare efficiently

Use the current exam page to define scope, then build a sandbox environment and perform the tasks yourself. Configure permissions, screens, fields, workflows, boards, automation, and notifications. Deliberately create mistakes and then diagnose them. Explain why one scheme should be shared while another should remain project-specific. Practice migrations or configuration changes with rollback and communication in mind.

For agile project work, a broader discussion of Scrum mastery can reinforce the process concepts behind the tool. The certification is strongest when candidates can connect Jira configuration to how teams actually plan, execute, support, and improve work.

Permissions are one of the most important admin topics

Jira permissions can be difficult because access is influenced by organization settings, product access, project permissions, issue security, roles, groups, and sometimes app-specific controls. Certification candidates should learn to troubleshoot permissions from the user's perspective: what action is failing, what scope controls it, and which group or role grants the capability?

Over-permissioning is as problematic as under-permissioning. Good administrators avoid granting broad global rights to solve a local problem. They design roles and groups that can be reviewed, explain why access exists, and support least privilege without making normal work impossible.

Workflow design should model real decision points

Workflows are often overcomplicated because teams convert every minor activity into a status. A better workflow represents meaningful state changes that affect ownership, reporting, automation, or governance. Conditions, validators, and post-functions should be used deliberately and tested for unexpected side effects.

Certification practice should include reviewing an existing workflow and simplifying it. Ask whether each status communicates useful information, whether transitions are clear, and whether reporting accurately represents work. This is a stronger administrative skill than merely knowing how to add a transition.

Service management introduces customer-facing constraints

Jira Service Management administrators must think about both agents and customers. Request types should be understandable to the requester, forms should collect enough information without becoming burdensome, queues should support triage, and SLAs should measure commitments that the service organization can actually manage. Automation can route and update work, but poorly designed rules can create noise or hide accountability.

Knowledge management is another important dimension. Linking service workflows with clear, maintained knowledge content can reduce repetitive requests and improve consistency. Administrators should understand the operational relationship between the portal, request data, knowledge, approvals, and fulfillment.

Certification status should be checked before scheduling

Atlassian's catalog is changing as Cloud becomes the dominant platform and some older certifications retire. That makes date-aware research essential. A study plan that begins in late 2026 may span a scheduled retirement or exam refresh, so candidates should confirm the live certification page before purchasing an exam.

Older ACP codes still have value for historical navigation and for teams maintaining legacy environments, but they should not drive a new certification decision when Atlassian has announced a replacement or retirement.

Dashboards and reports can only be trusted when teams use fields, statuses, estimates, and workflows consistently. Administrators therefore influence reporting quality long before a chart is built. Duplicate fields, ambiguous statuses, inconsistent resolutions, or project-specific shortcuts can make portfolio reporting misleading.

A certification-ready administrator should understand the relationship between configuration and data quality. Before adding a new field, ask whether an existing field can serve the purpose. Before creating a status, determine what decision it supports. Before changing a workflow, consider what historical reports and automations depend on the current values.

Many candidates practice only the happy path: create a workflow, configure a board, add an automation rule. Better preparation also includes rollback and diagnosis. Export or document the original configuration, make a controlled change, observe the effect, and then restore service. Review audit logs and explain why the system behaved as it did.

This approach mirrors real administration, where the ability to recover safely is as important as the ability to build. It also exposes hidden dependencies that are difficult to learn from documentation alone.

Atlassian Cloud changes continuously, so administrators must be comfortable learning from release notes, sandbox testing, and documentation rather than depending on an interface remaining unchanged. Certification should therefore validate concepts that survive UI changes: permissions, workflow logic, project configuration, service behavior, governance, automation design, and troubleshooting. That mindset also makes recertification or future credential updates easier because the administrator understands the underlying operating model.

A useful administration exercise is to make a controlled change in a sandbox, document the expected effect on permissions, workflow, automation, and reporting, then verify the outcome with accounts that represent different user roles. This exposes unintended dependencies before they reach production and builds the recovery discipline expected of a cloud administrator.