ACP-120 logo
Focused certification exam prep
Start practice

ACP-120 Domain 6: Workflows and Automation (5-10%) - Complete Study Guide 2026

TL;DR
  • Domain 6 covers Workflows and Automation and represents 5-10% of the ACP-120 exam's up to 75 questions.
  • Expect scenario-based questions requiring you to design or troubleshoot workflow transitions, conditions, validators, and post functions.
  • Jira Cloud automation rules - including triggers, conditions, branches, and actions - are fully testable and differ from Server/Data Center behavior.
  • Workflow schemes control which workflow applies to which issue type; misconfiguring them is a classic exam trap.

Domain 6 Overview: What Workflows and Automation Covers

Within the eight domains of the ACP-120 exam, Domain 6 - Workflows and Automation - sits at the lighter end of the weighting scale at 5-10% of total exam content. That translates to roughly four to eight questions out of the exam's maximum of 75. Smaller weight does not mean easier questions; this domain is the one where scenario-based configuration reasoning is most likely to trip up candidates who studied conceptually without hands-on practice.

If you are building a holistic picture of where Domain 6 fits relative to everything else, the ACP-120 Exam Domains 2026: Complete Guide to All 8 Content Areas shows you the full weight distribution across all eight domains and helps you allocate study time proportionally. Domain 3 (Product and Project Access and Permissions) dominates at 30-35%, so Domain 6 should receive focused but time-boxed attention rather than weeks of deep study.

What the domain actually tests breaks down into two broad areas:

  • Workflows - statuses, transitions, conditions, validators, post functions, and scheme assignment
  • Automation - Jira Cloud's native automation engine: triggers, conditions, branches, and actions, including cross-project rules and rule management permissions

Both areas are grounded in how a Jira Cloud administrator configures, publishes, and troubleshoots these features inside the product - not theoretical descriptions of what they are.

Workflow Fundamentals You Must Master

Statuses, Transitions, and the Workflow Diagram

A Jira Cloud workflow is a defined sequence of statuses and the transitions that move issues between them. Every workflow must have at least one status, and every transition connects a source status to a destination status. The global transition is a specific concept you must understand: it allows an issue to move to a destination status from any current status, which is useful for things like a "Cancel" transition but can create governance problems if applied carelessly.

On the ACP-120, you will encounter questions that describe a business scenario - for example, "A developer needs to be able to reopen an issue from the Done column without going through QA review" - and ask you to identify the correct transition configuration. These are not abstract questions; they require you to mentally trace through the workflow diagram and determine which transition type, condition, or validator achieves the described behavior.

Workflow Components Tested in Domain 6

Each of these components can appear individually or in combination within a scenario question. Know what each one does and when to use it.

  • Conditions - Restrict which users can execute a transition (e.g., only members of a specific group)
  • Validators - Enforce data requirements before a transition completes (e.g., a required field must have a value)
  • Post Functions - Actions executed automatically after a transition fires (e.g., assign issue, update a field, send email)
  • Properties - Key-value metadata on statuses or transitions used to control board column mapping and other behaviors
  • Triggers - Workflow-level triggers that fire transitions in response to external events (distinct from automation triggers)

Active vs. Draft Workflows

In Jira Cloud, a workflow that is currently assigned to a live project is considered active. You cannot edit an active workflow directly - you must create a draft, make changes, and then publish the draft. This distinction is a frequent source of exam questions. If a scenario describes an administrator who cannot save changes to a workflow, the correct answer almost always involves the concept of creating and publishing a draft rather than editing in place.

The publish process also forces Jira to migrate existing issues. If a status is removed from a workflow during publication, Jira will prompt the administrator to map those issues to an existing status. Questions about this migration step test whether you understand the operational impact of workflow changes on live projects.

Cloud-Specific Behavior: Jira Cloud's workflow editor differs visually and functionally from Server and Data Center. The ACP-120 tests only Cloud behavior. Post functions available in Cloud may differ from those you have used in on-premises environments. If your hands-on experience is primarily with Server or Data Center, spend extra time in a Cloud sandbox to recalibrate your mental model before exam day.

Jira Automation Rules: Components and Configuration

The Four Building Blocks of Every Rule

Jira Cloud's built-in automation engine (formerly acquired as Code Barrel's Automation for Jira) is fully integrated into the platform and heavily testable in Domain 6. Every automation rule is built from the same four-part structure:

  1. Trigger - The event that starts the rule (e.g., issue created, field value changed, scheduled)
  2. Conditions - Optional filters that determine whether execution continues (e.g., issue type is Bug, priority is High)
  3. Branches - Allow the rule to act on related issues (e.g., parent issues, sub-tasks, linked issues, or epic children)
  4. Actions - What the rule actually does (e.g., transition issue, assign user, create sub-task, send notification)

Exam questions in this area typically present a business requirement - "When all sub-tasks of an epic are resolved, automatically transition the epic to Done" - and ask you to identify the correct trigger, branch, and action combination. Getting the branch type wrong (using sub-task branch when epic children branch is needed) is a common mistake that the exam specifically probes.

Rule Scope and Permission to Manage Automation

Automation rules in Jira Cloud have three scope levels: project rules (apply within a single project), cross-project rules (apply across multiple specified projects), and global rules (apply across the entire site). Project administrators can create and manage project-scoped rules. Cross-project and global rules require Jira Administrator permissions.

This permission model is exactly the kind of detail the ACP-120 tests. A scenario might describe a project admin who is unable to create an automation rule that triggers across two projects and ask why. The answer involves scope - cross-project rules are outside the project admin's permission boundary.

Key Takeaway

Automation rule scope directly ties to the permission model tested in Domain 3. If you find Domain 6 automation questions confusing, revisit the ACP-120 Domain 3: Product and Project Access and Permissions (30-35%) - Complete Study Guide 2026 to reinforce how administrator roles interact with automation scope.

Smart Values and Conditional Logic

Jira automation supports smart values - a templating syntax that lets you reference issue data dynamically within rule actions. For example, {{issue.summary}} inserts the issue's summary text into a comment or notification body. You do not need to memorize every smart value for the ACP-120, but you should understand that they exist, what they enable, and how they are used in action configuration. Questions may present a partially built rule and ask which smart value or conditional statement completes it correctly.

Workflow Schemes and Project Association

A workflow scheme maps workflows to issue types within a project. By default, a project may use a single default workflow for all issue types, or it may assign distinct workflows to specific issue types - for example, a separate Bug workflow with dedicated triage statuses versus a simpler Story workflow.

Configuration When to Use Key Admin Consideration
Single workflow for all issue types Simple projects with uniform process needs Easiest to maintain; changes affect all issue types simultaneously
Issue type-specific workflows Projects where Bugs, Stories, and Epics follow different processes Requires separate workflow maintenance; scheme must be updated when issue types change
Shared workflow scheme across projects Organizations standardizing process at scale Publishing a draft change affects all projects using the scheme simultaneously

Understanding workflow schemes also connects directly to the scheme-heavy content in ACP-120 Domain 4: General Project Configuration (10-15%) - Complete Study Guide 2026, where scheme inheritance and project-level configuration decisions are addressed in more depth. The ACP-120 frequently tests administrators on the downstream effect of modifying a shared scheme - a question might ask what happens to Project B when you publish a draft workflow change originally requested for Project A, and both projects share the same workflow scheme.

Team-Managed vs. Company-Managed Projects: Workflow behavior differs significantly between project types in Jira Cloud. Team-managed projects use simplified, non-shared workflows that project admins can edit independently. Company-managed projects use the full workflow scheme model with shared workflows. The ACP-120 focuses on company-managed project administration, so ensure your study and practice environment reflects that project type.

How Domain 6 Questions Appear on the ACP-120

The ACP-120 uses multiple-choice, multiple-response, and scenario/configuration-reasoning items across its 75-question format with a 180-minute time limit. Domain 6 questions lean heavily toward the scenario and configuration-reasoning format. You will rarely see a simple "what is a post function?" recall question. Instead, expect prompts structured like:

  • "A team wants issues to automatically be assigned to a specific user when they are moved to the In Review status. Which workflow component should the administrator configure?"
  • "An automation rule is not firing when a sprint completes. The rule uses a Scheduled trigger set to run daily. What is the most likely cause?"
  • "A validator has been added to the Resolve transition requiring the Resolution field to have a value. A project admin reports that developers can still close issues without setting Resolution. What should the administrator check first?"

These questions reward administrators who have genuinely configured these features in Cloud. If you want to understand how this difficulty level compares to the exam overall, the How Hard Is the ACP-120 Exam? Complete Difficulty Guide 2026 breaks down question complexity across all domains and explains what separates passing candidates from those who fall short of the 63% threshold.

For targeted preparation, working through Best ACP-120 Practice Questions 2026: What to Expect on the Exam will help you recognize the structure of workflow and automation scenarios before you encounter them under exam conditions. You can also reinforce your readiness with the full-length simulations at ACP-120 Exam Prep practice tests.

Scheduling Domain 6 in Your Prep Timeline

Because Domain 6 carries 5-10% weight, it should not anchor your study schedule - but it should not be skipped. A practical approach is to study it in parallel with Domain 7 (Notifications and Email, also 5-10%) during a single focused week, leaving the bulk of your preparation for Domain 3 and Domain 5.

Week 1

Permissions and Access Foundation (Domain 3)

  • Permission schemes, project roles, global permissions
  • This domain is 30-35% of the exam - start here
Week 2

Issue Configuration (Domains 4 and 5)

  • General project configuration, issue types, fields, screens
  • Screens and field configurations feed directly into workflow validators
Week 3

Workflows, Automation, and Notifications (Domains 6 and 7)

  • Build and publish a full workflow with conditions, validators, and post functions in a sandbox
  • Create automation rules covering all four trigger categories
  • Review workflow scheme association and project type differences
Week 4

Full Review and Practice Exams

Configuration Mistakes That Show Up as Wrong Answers

The most effective way to prepare for Domain 6 is to understand where administrators make real configuration mistakes - because those mistakes become the plausible wrong answers in exam questions. These are the patterns that appear most frequently:

  • Confusing conditions and validators: Conditions control who can trigger a transition; validators control what data state must be present before the transition completes. A question about preventing a transition unless a field has a value is about validators, not conditions. Getting these reversed is a top source of incorrect answers.
  • Forgetting to publish the draft: Editing an active workflow creates a draft, but that draft has no effect until published. Scenario questions about "why isn't my change working" often hinge on this step being skipped.
  • Using the wrong automation branch: Sub-task branch and epic children branch are different. Using a linked issues branch when the business requirement involves parent-child hierarchy will produce a rule that never fires correctly.
  • Assuming project admin scope for cross-project automation: Project administrators cannot create or manage cross-project or global automation rules. This is tested directly and connects to the permission hierarchy in Domain 3.
  • Editing a shared workflow without understanding scheme impact: If a workflow is shared across multiple projects via a workflow scheme, publishing a change affects all of them. Exam questions test whether candidates recognize this blast radius.

Domain 5 content is closely related here - particularly around field configuration and screen schemes that interact with workflow validators. Reviewing the ACP-120 Domain 5: Issue Types, Fields and Screens (15-20%) - Complete Study Guide 2026 before drilling Domain 6 will give you a stronger foundation for understanding why certain validators behave the way they do.

Also check the complete ACP-120 Study Guide 2026: How to Pass on Your First Attempt for a unified preparation roadmap that integrates all eight domains into a coherent approach toward the 63% passing score.

Frequently Asked Questions

How many questions from Domain 6 will appear on the ACP-120?

Domain 6 represents 5-10% of the exam. With a maximum of 75 questions, you can expect roughly four to eight questions covering workflows and automation. The exact number varies per exam form, but this domain is consistently among the lighter-weighted ones.

Does the ACP-120 test Jira automation or only native Jira workflows?

Both are in scope for Domain 6. The exam covers native Jira Cloud workflow configuration (statuses, transitions, conditions, validators, post functions) and Jira Cloud's built-in automation engine (triggers, conditions, branches, actions, rule scope, and permission management). You should be comfortable with both in a hands-on Cloud environment.

Are team-managed project workflows covered on the ACP-120?

The ACP-120 is focused on Jira Cloud administration at the company-managed project level, where the full workflow scheme model applies. While you should understand the conceptual difference between team-managed and company-managed workflows, the detailed configuration questions center on company-managed projects and their shared workflow schemes.

What is the difference between a workflow trigger and an automation trigger in Jira Cloud?

A workflow trigger is a specific feature within a workflow transition that fires the transition in response to an external event (such as a Bitbucket commit). An automation trigger is the starting event of an automation rule (such as issue created or field value changed). They are separate mechanisms that serve different purposes, and the ACP-120 may test whether you can distinguish them in a given scenario.

Is it worth spending a lot of time on Domain 6 given its low exam weight?

A focused week of hands-on practice in a Cloud sandbox is the right investment - not multiple weeks. Because Domain 6 questions are scenario-based and configuration-specific, rote memorization is less effective than actually building workflows and automation rules. Get the fundamentals solid, then redirect study time toward higher-weight domains like Domain 3 and Domain 5.

Ready to Start Practicing?

Test your Domain 6 knowledge with full-length ACP-120 practice exams that mirror the real exam's scenario-based workflow and automation questions. Identify your gaps now so you can fix them before exam day.

Start Free Practice Test

Ready to pass your ACP-120 exam?

Put this into practice with free ACP-120 questions across every exam domain.