ACP-620 study plan

Configure and compare global settings such as application properties, default user time zone, and attachment size limits in a sandbox site.

Trace how a system setting change propagates to project and issue behavior by testing it against at least three sample issues.

Diagram the relationship between global permissions, project permissions, and issue-level security in a one-page reference you can redraw from memory.

Audit the administration menu structure and record every setting you cannot yet explain in a running gap list.

Configure mail handlers, incoming and outgoing mail, and verify a test message round-trip in the sandbox.

Set up and interpret logging levels and the support zip / system diagnostics tools to diagnose a deliberately broken configuration.

Explain and demonstrate how application links and general configuration interact with base URL and indexing.

Re-run the gap list from week 1 and close at least five items with hands-on verification.

Create three projects using different templates and compare the resulting schemes each template assigns.

Configure project-level settings including project category, project lead, default assignee, and issue security.

Map the scheme-sharing model by building a table of which projects share which permission, notification, and issue type schemes.

Demonstrate how changing a shared scheme affects multiple projects, then restore the original state.

Build a custom field of each major type and record where each type is and is not usable in screens and contexts.

Configure field contexts and field configuration schemes to make one field required in one project and optional in another.

Design and assemble a screen scheme covering create, edit, and view operations, then verify the behavior per issue operation.

Explain issue type schemes and demonstrate moving an issue type between projects without orphaning issues.

Build a workflow from scratch with at least five statuses, including a global transition and a self-loop.

Add and test a condition, a validator, and a post function on the same transition and explain evaluation order.

Configure a post function that updates a field and one that fires an event, then verify the resulting notification and history entry.

Use the workflow designer and the text/diagram views to audit an existing workflow for unreachable statuses.

Design a permission scheme from a written requirements list, using groups, project roles, and single users appropriately.

Demonstrate the difference between a group and a project role by changing membership and observing access changes.

Configure an automation rule with a trigger, a condition, and an action, and verify it fires only under intended conditions.

Set up a notification scheme and confirm which events reach which recipients, including a suppressed case.

Perform a CSV import into a sandbox project and reconcile field mapping, date formats, and user attribution.

Export project data and verify integrity by comparing issue counts and key field values before and after.

Configure an issue link type and demonstrate linking behavior plus the effect on search and reporting.

Set up one integration touchpoint such as a webhook or incoming mail channel and confirm the payload reaches Jira.

Re-take a timed practice set weighted to the heaviest domains and log every missed question by domain.

Re-teach your three weakest objectives from memory on a blank page, then verify against documentation.

Rebuild one workflow and one permission scheme from scratch under time pressure without notes.

Consolidate the running gap list into a final one-page cheat sheet of facts you repeatedly missed.