ACP-100 study materials
ACP-100 study resources

ACP-100 study plan

ACP-100 · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Application and Project Configuration

  • Map every global setting that affects project creation, and record which ones are instance-wide versus project-scoped.

  • Create a company-managed project from scratch and document each configuration screen you pass through.

  • Configure issue type schemes, field configurations, and permission schemes for that project, then explain in writing why each choice was made.

  • Compare company-managed and team-managed projects by listing what each model lets an administrator control.

Your checkpoint

A written configuration log for one fully built company-managed project, listing every scheme applied, the setting source, and a short justification for each choice.

Week 2

Application and Project Configuration & Issue Types, Fields, Screens, and Schemes

  • Build a custom field of each major type and assign it to the correct field configuration context.

  • Design two screens (create and edit) and attach them through a screen scheme to the right issue operations.

  • Trace how a field travels from custom field to field configuration to screen to issue type scheme, and write the chain down.

  • Diagnose three deliberately broken field setups, such as a required field missing from the create screen.

Your checkpoint

A field-and-screen traceability table covering at least eight custom fields, showing field, context, configuration, screen, and issue types for each.

Week 3

User Management, Groups, and Permissions

  • Create groups and assign global permissions, then predict the effective permission for a test user before verifying it.

  • Build a project role structure and map roles to groups and individual users in a permission scheme.

  • Apply issue-level security and an issue security scheme, then test visibility with users in different roles.

  • Explain how permission schemes, roles, groups, and global permissions interact when they conflict.

Your checkpoint

A permission matrix for a three-role, two-group test project, plus a written explanation of at least two conflict scenarios and how Jira resolves them.

Week 4

Workflows, Transitions, and Conditions/Validators/Post Functions

  • Draw a workflow with at least five statuses, including a global transition and a self-loop.

  • Attach a condition, a validator, and a post function to specific transitions and describe the exact effect of each.

  • Configure a post function that updates a field and one that fires an event, then verify both in a test issue.

  • Explain the difference between workflow schemes and workflow editing, and when a draft and publish cycle is required.

Your checkpoint

A working custom workflow with documented transition logic, plus a one-page table listing every transition, its conditions, validators, and post functions.

Week 5

Workflows, Transitions, and Conditions/Validators/Post Functions & Jira Automation and Notification Schemes

  • Build an automation rule with a trigger, a condition, and two actions, and confirm it runs correctly.

  • Configure a notification scheme that sends different events to different groups and roles.

  • Explain when to use automation versus a workflow post function versus a notification, and give an example of each.

  • Test a rule that fails and use the audit log to find the cause.

Your checkpoint

Two working automation rules with audit-log screenshots described in text, plus a comparison note on automation, post functions, and notifications.

Week 6

Jira Automation and Notification Schemes & Dashboards, Filters, and Reporting

  • Build three filters using JQL, including one with a function such as a date or user function.

  • Assemble a dashboard with at least three gadgets fed by those filters and set sharing correctly.

  • Create a filter subscription and describe who receives it and how often.

  • Explain how filter and dashboard sharing permissions affect who sees the underlying issues.

Your checkpoint

A documented dashboard with three gadgets, the JQL behind each filter, and a sharing-permission explanation.

Week 7

Integrations, Apps, and Data Migration

  • Plan a CSV import, mapping each column to a field and choosing the correct date format and delimiter.

  • Describe how to migrate issues, attachments, and users between projects without losing history.

  • Identify the data that a project import cannot carry over and how to handle it.

  • Evaluate an app installation for its permission scope and effect on existing schemes.

Your checkpoint

A migration runbook for a sample project, including a field mapping table, a pre-import checklist, and a rollback plan.

Week 8

Application and Project Configuration & User Management, Groups, and Permissions & Issue Types, Fields, Screens, and Schemes & Workflows, Transitions, and Conditions/Validators/Post Functions & Jira Automation and Notification Schemes & Dashboards, Filters, and Reporting & Integrations, Apps, and Data Migration

  • Rehearse every domain with timed practice sets and log the score for each.

  • Revisit the two lowest-scoring domains and rebuild the specific configurations you got wrong.

  • Explain aloud, without notes, how a field, a permission, and a workflow transition each resolve.

  • Review your week-one configuration log and correct any errors you now spot.

Your checkpoint

A final scorecard by domain with a short remediation note for each area still below target.

Milestones

Week 2: You can build a project with custom fields, screens, and issue types from memory in under 30 minutes without consulting notes.

Week 4: You can predict a user's effective permission and the outcome of a transition before testing, and you are right at least 80 percent of the time.

Week 6: You have a working automation rule and a shared dashboard, and you can explain both without notes.

Week 8: Your practice scores are at or above 80 percent in every domain, with no domain below 70 percent.