Atlassian ACP-420: Managing Jira Service Projects in Cloud

ACP-420 is Atlassian's current professional certification for Managing Jira Service Projects for Cloud. It is designed for Jira Service Management project administrators who configure company-managed service projects for agents and customers. Atlassian refreshed the certification in 2025 to reflect newer Jira Service Management Cloud capabilities, and in September 2026 it explicitly confirmed that the planned Jira administration changes for 2027 do not retire ACP-420.

The exam is built around practical administration rather than abstract IT service-management vocabulary. Current Atlassian guidance describes a three-hour exam with up to 75 questions and a 66% passing score. The credential is valid for 24 months. More important than those logistics is the expected experience: Atlassian recommends real administration practice because the questions ask candidates to choose configuration that fits a service-management scenario, not merely identify where a menu exists.

ACP-420 is about the service-project administrator role

Within Atlassian certifications, ACP-420 sits at the intersection of Jira administration and service delivery. The administrator does not own every global Jira setting, yet has enough project-level responsibility to shape how customers submit requests, how agents work those requests, how service targets are measured and how information flows through the project.

That role boundary is important. A service project is not simply a software project with a different name. It has customer-facing channels, request types, queues, service-level agreements, knowledge features, portal behavior and service-specific permissions. The admin has to understand how those pieces interact with Jira's underlying issue model.

A general Jira foundation helps with issues, fields, workflows, permissions and JQL, but ACP-420 expects candidates to apply those mechanics to the experience of customers, agents, collaborators and service owners.

Users, roles and permissions define both sides of the service desk

Jira Service Management separates internal product users from customers who may only interact through the portal or other request channels. Agents need product access and appropriate project roles to work requests. Customers can be organized in customer organizations and may have portal access without being licensed as agents. Collaborators can participate in ways that differ from full service agents.

ACP-420 preparation should therefore start with identity boundaries. Candidates need to distinguish global product access, project roles, permission schemes, customer permissions and portal-sharing settings. A configuration that gives an internal user visibility in Jira may not determine whether an external customer can find a request in the portal, and a customer-facing setting does not automatically grant agent capabilities.

Scenario questions often become easier when the audience is identified first. Is the person an agent, a Jira user without an agent license, an external customer, a member of a customer organization, or an administrator? Once that is clear, the candidate can reason about the narrowest setting that controls the requested behavior.

Request types translate customer language into Jira issues

Customers should not need to understand Jira's internal issue-type architecture before asking for help. Request types provide a service-oriented layer that gives each kind of request a recognizable name, form and portal location while mapping it to an underlying Jira issue type.

This design creates a practical configuration problem. The admin must decide which information customers should provide, which fields agents need later, what should be hidden or preset, and how forms should guide the requester without collecting unnecessary data. A good request experience reduces back-and-forth because the ticket arrives with enough context to route and diagnose it.

Multiple channels can feed the same service project. Portal submissions, email and other supported intake methods can create requests, but each channel has different constraints. The administrator should understand how request types, email handling and form design affect the issue that agents ultimately see.

Agent-facing configuration turns incoming demand into manageable work

Queues are one of the most visible administrative tools because they give agents operational views of work. A queue is useful only if its filter logic matches the workflow and service process. Poorly designed queues can hide urgent requests, duplicate the same work across views or leave tickets without a clear owner.

JQL remains important here because queues, reports and many operational views depend on filters. Candidates should be comfortable reading conditions based on status, request type, priority, assignee, organization, SLA state and other fields. They should also know when a project setting, workflow change or field configuration is a better answer than endlessly complicating the query.

Issue layout and agent-visible fields matter for the same reason. Service agents need the context required to act quickly, but a crowded issue view can bury the decisive information. The best configuration aligns the issue layout with the actual decisions an agent makes.

SLAs measure service commitments rather than ordinary due dates

Service-level agreements are a core Jira Service Management concept because they measure elapsed service time under defined conditions. An SLA can start, pause and stop based on request state, and calendars determine which hours count. Goals may vary by priority, request type or other criteria.

The important skill is to reason from the service promise. If a team promises a first response within a defined window, the timer should reflect when a request enters a state that requires attention and when a qualifying response occurs. If the clock should pause while waiting for a customer, that state must be represented correctly. A target that looks right on paper can produce misleading performance data if its start, pause or stop logic is wrong.

SLAs also feed queues and reports. A near-breach queue can help agents prioritize work, while trend reports can reveal where service commitments are consistently difficult to meet. ACP-420 therefore treats SLA configuration as part of an operating system for service work, not as a decorative metric.

The customer portal and notifications shape trust in the service

The portal is the customer's view of the service desk. Administrators organize request types into portal groups, control what customers can discover, configure branding and help text, and decide how requests can be shared. Small configuration choices can substantially change whether customers understand where to go and what will happen next.

Notifications must also be considered from the customer's perspective. Jira Service Management has customer notifications as well as Jira's internal notification behavior. The admin should know which events generate messages, how templates and recipients work, and how to avoid either silence or excessive mail.

Good portal design and good notification design support the same outcome: customers can submit the right request, understand its status and know when they need to act. The exam tends to reward configurations that solve that experience directly rather than workarounds that only make the agent side look correct.

Knowledge management connects Jira Service Management with Confluence

Knowledge articles can deflect repetitive requests and give agents a reusable source of answers. Jira Service Management can surface knowledge content in the portal and during request creation, but the underlying knowledge base relationship often involves Confluence. Understanding the practical boundary between the two products helps administrators design the experience correctly.

The broader comparison between Jira and Confluence is useful here because the products serve different purposes: Jira structures work and service requests, while Confluence structures collaborative knowledge. In a service-management environment, they complement rather than replace each other.

Knowledge quality still matters more than simply enabling the integration. Articles should answer real recurring questions, use language customers can search, and be maintained when products or procedures change. A technically connected but stale knowledge base can increase confusion instead of reducing demand.

Reporting should answer operational questions

Reports are useful when they help a service owner decide what to change. Request volume can reveal demand patterns. SLA performance can identify recurring breaches. Resolution time can expose bottlenecks. Customer satisfaction can provide another perspective on service quality. The administrator needs to know what a report actually measures before treating it as evidence.

Filters, date ranges and status definitions can change the meaning of a chart. For example, a resolution metric built around completed requests answers a different question from a queue showing currently open work. A strong candidate reads the scenario, identifies the decision being made, and chooses the view that represents the relevant population.

Reporting also connects back to configuration quality. If request types are inconsistently used or statuses do not reflect meaningful workflow stages, the reports will inherit that ambiguity. Good analytics begin with a service model that captures the distinctions the team cares about.

Automation is powerful when scope and ownership are clear

Automation can route requests, set fields, notify teams, create linked work, escalate conditions and reduce repetitive agent actions. ACP-420 expects administrators to understand triggers, conditions, branches and actions well enough to predict what a rule will do in a real project.

The strongest approach is to reason about automation as a controlled process. What event starts the rule? Which requests qualify? Which actor or permissions does the rule use? Could it trigger itself again? Does the action change data that another rule depends on? A technically valid rule can still be a poor design if its scope is too broad or its effects are hard to trace.

Automation should also complement, not substitute for, clear workflows and permissions. If a process requires a formal approval or a protected transition, the underlying model should express that requirement rather than relying entirely on a hidden rule.

ACP-420 is adjacent to Jira project administration, not interchangeable with it

The ACP-620 Managing Jira Projects for Cloud certification focuses on Jira software project creation, boards, project management, automation and reporting. ACP-420 shares some Jira fundamentals but adds the customer-and-agent service model, request types, portals, SLAs, knowledge management and service-specific configuration.

This distinction becomes especially important as Atlassian reshapes its certification catalog. ACP-620 is scheduled to retire in January 2027 as selected project-administration content moves into Jira Administration for Cloud. Atlassian has explicitly said that this change does not retire ACP-420. Service-project administration remains a separate current specialization.

Preparation works best as repeated configuration and diagnosis. Reading the exam topics is necessary, but hands-on practice is what connects the settings. Build a test service project and deliberately change customer permissions, request types, queues, SLAs, portal groups, notifications, knowledge settings, reports and automation rules. Then inspect the result as both an agent and a customer.

When a scenario fails, trace the configuration path instead of guessing. If a customer cannot see a request, identify the sharing and customer-access controls. If an SLA behaves unexpectedly, inspect its conditions and calendar. If a queue omits tickets, test the JQL. If an automation rule does nothing, verify the trigger, condition, scope and actor.

ACP-420 ultimately validates the ability to turn Jira Service Management Cloud into a coherent service environment. Candidates who understand the relationships among customers, agents, requests, workflows, SLAs, knowledge, reporting and automation are much better prepared than those who memorize isolated settings.

ExamSnap's Atlassian ACP-420 Practice Test Questions and Exam Dumps, study guide, and video training course are complicated in premium bundle. The Exam Updated are monitored by Industry Leading IT Trainers with over 15 years of experience, Atlassian ACP-420 Exam Dumps and Practice Test Questions cover all the Exam Objectives to make sure you pass your exam easily.