When I began working on our recent Oracle ERP implementation, I quickly realized just how overwhelming it could get – hundreds of tasks, defects, test cases, and change requests all flowing through Jira. Manual tracking wasn’t going to cut it.
That’s when I dove deep into Jira Automation. What started as a necessity soon turned into a learning journey. I explored, experimented, and ultimately ideated over 20 automation use cases tailored to the needs of a PMO.
In this post, I’m sharing what I learned – real automation examples we implemented that saved hours of manual work, reduced errors, and kept the entire program moving efficiently. These are practical ideas that any PMO managing a complex ERP or large-scale project should consider.
ERP programs are challenging by nature – with multiple workstreams, cross-functional teams, and constantly shifting priorities. Smart automation helped us stay ahead – and I hope these lessons can help you too.
Jira Automation helped us:
- Ensure process consistency across workstreams
- Minimize human error
- Speed up transitions and reduce admin overhead
- Keep teams & dashboards in sync with real-time notifications
Automation rules:
Automations in Jira are called rules. You can create automation rules using 4 components:
- Trigger: When a user performs a trigger action the automation rule will run
- Condition: This element ensures that the automation is triggered if all of the conditions are met
- New branch: This element creates a branch that allows to set up separate conditions for certain elements like subtasks of a parent issue
- New action: This element defines what the system will do when the user triggers a rule and all of the conditions are met
20 Jira Automation Use Cases That Actually Worked for Us
1. Close Parent When All Child Tasks Are Closed
When every sub-task under a parent issue is completed, the parent is auto-closed. This kept our boards clean without waiting on someone to manually transition.
2. Close Child Tasks When Parent Task Is Closed
Reverse logic also helped. If a parent was marked “Done,” any lingering sub-tasks would automatically be transitioned to “Closed.”
3. Withdraw Child Tasks When Parent Is Withdrawn
Massive time-saver: when a parent story or change was withdrawn, all associated sub-tasks were auto-withdrawn too – no manual cleanup required.
4. Email Notification on Label Updates
We triggered email alerts whenever a specific label (like “Critical” or “Regression”) was added – this was especially helpful in defect management.
5. Auto-Create Tasks / Sub-Tasks with Pre-Filled Fields
Whenever certain parent issue types were created, Jira automatically generated tasks / sub-tasks with all required fields pre-populated. No one had to remember what to add.
6. Disable Auto-Creation When Not Needed
We used smart conditions to disable auto-creation in specific scenarios (like for fast-track tickets), so we didn’t over-engineer simple cases.
7. Email Alerts for Overdue Tasks
Assignees got auto-reminders when their tasks were overdue – daily or weekly, depending on severity. This helped keep things moving without manager follow-ups.
8. Transition Parent Workflow StatusBased on Child Summary & Status
For example, when a “Testing – Passed” sub-task was completed, and other conditions were met, the parent task automatically moved to the next phase (like “Ready for UAT”).
9. Status Roll-Up in Jira Structures
We used automation to roll up statuses from sub-tasks and linked issues into the main Structure view, giving leadership an accurate summary at any time.
10. Copy Labels from Parent to Child
To maintain context, we copied labels from the parent issue to its sub-tasks – almost like syncing metadata.
11. Add Labels Based on Other Field Values
We used automation to auto-tag issues when certain field values were entered – like tagging a ticket as “Finance” if the module field = “GL.”
12. Add Watchers Based on Workstream or Label
As soon as a label like “Security” was applied, automation added the relevant team members as watchers – keeping them in the loop automatically.
13. Auto-Assign Defects/Issues Based on Workstream
When a defect was created, we parsed the workstream field and updated the assignee accordingly. No need for manual triaging.
14. Notify Teams via Auto-Comments on Defects
Instead of tagging teams manually in comments, automation added comments like @Security_Team, please review. This ensured proper notification every time.
15. Update Sprint Based on Baseline Start Date
A more advanced rule – we mapped Sprint IDs to baseline dates and updated the sprint field automatically. It took effort to set up, but paid off during test cycles.
16. Copy Fields from Test/Execution to Defects
When defects were created from test executions, we automatically transferred fields like test case ID, scenario name, and environment info to the defect ticket.
17. Notify Teams on New Defects or CRs
Whenever a new defect or change request was logged, Jira automation alerted the appropriate team instantly – ensuring nothing sat idle for long.
18. Update Test Plan Once All Test Cases Are Passed
This automation kept our testing workflows sharp. When every test case linked to a test plan was marked as “Passed,” the test plan itself was automatically transitioned to “Completed.” It eliminated the need for manual monitoring and ensured instant visibility for test leads and stakeholders.
19. Update Test Cycle to the Defects Created via Test Case/Test Executions
To maintain traceability, we automated the process of linking defects back to the test cycle they originated from. When a defect was created directly from a test case or test execution, the associated test cycle was automatically populated in the defect. This made defect triaging and reporting far more accurate and efficient.
20. Prompt Change Request Creators with Required Context Questions
To ensure consistency and completeness in Change Request submissions, we set up an automation that prompts the requester with a structured set of questions.
Method 1: As soon as a CR is created, Jira posts an auto-comment (or pre-fills the description) asking for key details like release impact, business/technical implications, affected workstreams, and timelines for design/build. This helped reviewers make faster, informed decisions without chasing clarifications.
Method 2: You can automatically show those questions inside the Description field when someone creates a new Change Request (CR) issue – so they don’t forget to include critical information. This is done by setting a default template in the issue’s description field for the “Change Request” issue type.
22. Auto-Fill ID Field from Summary Name
When a task summary followed a standard format like “REP090 – Summary Text”, automation extracted the ID (e.g., REP090) and populated a custom field labeled ID#. This ensured consistency across records and simplified filtering and reporting.
That’s a wrap
Jira Automation became more than just a time-saver during our ERP implementation – it became a strategic enabler for our PMO. By automating routine tasks, we freed up time for higher-value work, reduced the risk of human error, and kept complex workflows running smoothly.
If you’ve built your own Jira automations or have ideas to share, I’d love to hear them. Let’s keep learning from each other
References:
Some of the sites which really helped to ideate many ideas are below:
https://www.atlassian.com/software/jira/guides/automation/overview#board-vs-project
https://www.geeksforgeeks.org/a-complete-guide-to-jira-automation-tool/
https://titanapps.io/blog/automate-jira-processes/
Discover more from LR Virtual Classroom
Subscribe to get the latest posts sent to your email.
LR Virtual Classroom 