How to Automatically Mark an Epic as Done When All Child Issues Are Completed in Jira
Managing large projects in Jira often involves working with Epics that contain multiple Stories, Tasks, and Subtasks. One common challenge for teams is keeping Epic statuses updated manually. Even when every child issue has been completed, the Epic itself often remains in an "In Progress" state until someone remembers to update it.
Fortunately, Jira Automation can handle this for you.
In this guide, we'll walk through how to create an automation rule that automatically transitions an Epic to Done whenever all of its child issues have been completed.
Why Automate Epic Status Updates?
Imagine a project with dozens of Stories and Tasks spread across multiple team members.
Without automation:
- Team members complete their work
- Stories move to Done
- Tasks move to Done
- The Epic remains In Progress
- Project dashboards become inaccurate
- Project managers must manually update Epics
With automation:
- Reduced manual effort
- More accurate reporting
- Better sprint tracking
- Cleaner project dashboards
- Improved team efficiency
The Goal
We want Jira to automatically:
- Detect when a Story, Task, or Subtask is moved to Done.
- Check whether all issues under the parent Epic are complete.
- If everything is completed, automatically transition the Epic to Done.
Prerequisites
Before creating the automation:
- Jira Automation enabled
- An Epic containing Stories or Tasks
- A workflow that allows the Epic to move to Done
Step 1: Open Jira Automation
Navigate to your Jira project and go to:
Project Settings > Automation
Click Create Rule.
Step 2: Add the Trigger
Select the "Issue Transitioned" trigger.
Configure:
To Status: Done
This means the automation runs whenever an issue is moved into the Done status.
Why Use Issue Transitioned?
Whenever a Story, Task, or Subtask is completed, Jira immediately checks whether the Epic should also be completed.
This creates real-time automation without requiring scheduled jobs.
Step 3: Filter the Issue Types
Add an Issue Type Condition.
Select:
- Story
- Task
- Subtask
This prevents the rule from running when an Epic itself is transitioned.
Step 4: Branch to the Parent Epic
Add a Branch Rule.
Choose:
- Parent
- Epic
- Related Issues (depending on your Jira setup)
Select the option that navigates from the completed issue to its Epic.
Step 5: Check Remaining Issues
Add a Related Issues Condition or JQL Condition.
Example logic:
status != Done
The goal is to verify that no child issues remain open.
If any Story or Task is still unfinished, the Epic should remain unchanged.
Step 6: Transition the Epic
Add a "Transition Issue" action.
Select:
Done
This automatically moves the Epic to the Done status.
Final Automation Flow
Issue Transitioned → Done
↓
Issue Type = Story / Task / Subtask
↓
Branch to Parent Epic
↓
Check if all child issues are Done
↓
Transition Epic to Done
Testing the Automation
Create a test Epic with a few Stories.
Example:
- Learn Node.js Basics
- Understand JavaScript for Backend Development
- Create Express Server
Move each Story to Done one by one.
The Epic should remain In Progress until the final Story is completed.
Once the last Story moves to Done, the Epic should automatically transition to Done.
Real-World Benefits
For Scrum Teams
Sprint reports stay accurate automatically.
For Project Managers
Less manual maintenance of Epics.
For Agile Coaches
More consistent workflows.
For Developers
Less administrative work and more focus on delivery.
Common Mistakes
Forgetting the Epic Branch
Without branching to the Epic, Jira may attempt to transition the Story instead.
Using the Wrong Status Name
Some workflows use Closed, Completed, or Resolved instead of Done.
Make sure the automation matches your workflow.
Workflow Restrictions
If the Epic workflow does not allow transitions to Done, the automation will fail.
Skipping the Child-Issue Check
Always verify that all child issues are complete before transitioning the Epic.
Monitoring the Automation
To troubleshoot:
Project Settings > Automation > Audit Log
The Audit Log shows successful executions, failures, validation errors, and rule performance.
Conclusion
Jira Automation helps eliminate repetitive project management tasks while improving reporting accuracy. By automatically transitioning an Epic to Done when all of its Stories and Tasks are completed, teams can maintain cleaner workflows, reduce manual effort, and improve project visibility.
For Jira beginners, this is one of the best automation rules to learn because it introduces the core concepts of Triggers, Conditions, Branches, and Actions while solving a real-world problem.
