ACP-420 study materials
ACP-420 study resources

ACP-420 case studies

ACP-420 · Put your knowledge to work in context.

ACP-420 is Atlassian's professional-level certification for people who administer Jira projects in Jira Cloud, as distinct from administering the whole instance. It suits project administrators, team leads and scrum masters with configuration duties, and consultants who set up and maintain projects for other people. The exam tests configuration judgement rather than trivia: choosing a project type, reasoning through how issue types, workflows, fields, screens, permissions, roles and boards fit together, and diagnosing why a project behaves as it does when a setting is inherited from a shared scheme. Preparation is hands-on. The ACP-420 case studies are 5 cases and about 3,952 words.

1

Facilities intake: picking a project type that survives a legal audit

Meridian's Jira Cloud site has 340 users, 11 company-managed projects and 4 team-managed projects. The facilities team asks for a new project to receive maintenance requests from all staff.

744 words, about 4 min
2

Post-acquisition consolidation of issue type and workflow schemes

Northwind acquired a supplier and now runs support (SUP) and engineering (ENG) as separate company-managed projects on one Jira Cloud site. SUP: 21,000 issues, issue types Bug, Task and Sub-task, workflow with Open, Waiting for Customer, Resolved, Closed.

793 words, about 4 min
3

Cost Center: required-ness, option bleed and a duplicate field

You are adding 'Cost Center', a single-select custom field, to a company-managed Jira Cloud site with 60 projects. Requirements: required on create for the 12 FIN projects; optional for OPS; invisible in HR.

718 words, about 4 min
4

Contractors, comments, and a filter on the open internet

Vantage runs a company-managed Jira Cloud project, VANT, with 480 licensed users. Roles: Administrators (group vant-admins), Developers (group vant-devs), Viewers (group vant-viewers).

808 words, about 4 min
5

Splitting one project into two boards without corrupting sprints

Two Scrum teams share company-managed project PLAT: 6,200 issues, one issue type scheme, and no component set on about 400 issues. Board ALPHA must show only issues with component Alpha; board BETA everything else.

889 words, about 4 min