- The Agile Coach
- Agile Manifesto
Agile project management
- Overview
- Project management intro
- Workflow
- Epics, stories, themes
- Epics
- User Stories
- Estimation
- Metrics
- Gantt chart
- Program management vs. project management
- Project baseline
- Continuous improvement
- Lean principles
- 3 pillars of Scrum
- Scrum Board
- Waterfall Methodology
- Velocity in Scrum
- What is Definition of Ready
- Lean vs. agile
- Scrumban
- Lean Methodology
- Sprint backlog
- Burn up chart
- 4 kanban principles
- 4 kanban metrics
- Program vs. Project Manager
- Gantt chart examples
- Definition of done
- Backlog grooming
- Lean process improvement
- Backlog refinement meetings
- Scrum values
- Scope of work
- Scrum tools
- Tools
- Workflow automation software
- Templates
- Task tracker
- Workflow automation
- Status report
- Workflow chart
- Project roadmap
- Project schedule
- Tracking software
- Roadmap tools
- Technology roadmap
- Project scheduling software
- Backlog management tools
- Understanding workflow management strategies
- Workflow examples
- Create project roadmap
- Sprint planning tools
- Sprint demo
- Project Timeline Software
- Top task management tools
- Product backlog vs. sprint backlog
- Top workflow management tools
- Project dependencies
- Task dashboard guide
- Sprint cadence
- Fast tracking
Product Management
- Overview
- Product Roadmaps
- Product Manager
- Tips for new product managers
- Roadmaps
- Tips for presenting product roadmaps
- Requirements
- Product analytics
- Product development
- Remote product management
- Minimal viable product
- Product discovery
- Product specification
- Product development strategy
- Product development software
- New product development process
- Product management KPIs
- Net Promoter Score (NPS)
- Product critique
- Prioritization frameworks
- Product features
- Product management tools
- Product Lifecycle Management
- 9 best roadmap software for teams
- Product launch checklist
- Product strategy
- Product engineering
- Product operations
- Portfolio management
- AI and product management
- Growth product management
- Product metrics
- Product release
- Feature request
- Product launch
- Product planning
- Product launch event
- Value Stream Management
- DevOps
Agile tutorials
- Overview
- Jira and Confluence sprint refinement
- How to do scrum with Jira
- Learn kanban with Jira
- Learn how to use Epics in Jira
- Learn how to create an agile board in Jira
- Learn how to use sprints in Jira
- Learn Versions with Jira
- Learn Issues with Jira
- Learn burndown charts with Jira
- Auto-create sub-tasks and update fields in Jira
- How to automatically assign issues with Jira Automation
- How to sync epics stories with Jira Automation
- Automatically escalate overdue issues in Jira
About the Agile Coach
- All articles
Auto-create sub-tasks and update fields in Jira
This guide reveals how to create a Jira automation rule that automatically creates sub-tasks when an issue is created.

By Kev Zettler
By Kev Zettler
Kev is a lead full stack web developer and serial entrepreneur with over a decade of experience building products and teams with agile methodologies. He is a passionate contributor, author, and educator on emerging open source technologies like DevOps, cryptocurrency, and VR/AR. In his free time, he participates in indie game development jams.
New Trigger
The first step is to select a trigger from the New trigger selection screen.
Next, find the Issue created trigger from the list of triggers
You can also find the Issue created trigger by searching for it in the search bar. Once you have selected the Issue created trigger, click the Save button.
New Condition
Next we will add a New condition component that will perform an action if the issue type is a Task. Click on the New Condition option on the Add component page.
Next, click the Issue fields condition:
This will direct you to the Issue fields condition configuration page. From the Field drop down, select Issue Type, change the Value to Task, and click the Save button.
New Action
To add an action to the rule, click on the New action item on the Add component page and filter for the Create sub-tasks action. Click the Create sub-tasks item to proceed.
On the Create sub-tasks page add one or more sub-tasks by clicking the Add another sub-task and fill in the Summary fields as you like. You can also configure the fields that you’d like in each sub-task.
When you click Add fields on the third sub-task the other two sub-tasks will be created as a separate action. You will be taken to a new Create Issue screen where you can configure additional fields. Click the Save button when finished.
Turn it on
This brings you to the Add component view where you can name the new Automation. Once you do, click the Turn it on button.
Try it out
Now that you created and activated a new automation rule, it’s time to try it out! Go back to your project, create a new issue, and set the type to Task.
Once you’ve created the new task, the automation rule will activate in the background. You can confirm if the automation rule succeeded by visiting the Audit Log. Navigate to Project Settings -> Automation, find your new Automation rule, and click the Audit Log tab. You should see a view similar to the following:
In the Audit log, if you see a row under the column Status labeled SUCCESS you’ve successfully built the automation rule. If you see the label SOME ERRORS, click on the Show More operations links to debug those errors. As you can see in the screenshot above we had to test and reconfigure our automation rule a few times before we were successful.Â
Once you have confirmed the automation rule operates successfully, return back to your project and you will see the new sub-tasks!
- The Agile Coach
- Agile Manifesto
Agile project management
- Overview
- Project management intro
- Workflow
- Epics, stories, themes
- Epics
- User Stories
- Estimation
- Metrics
- Gantt chart
- Program management vs. project management
- Project baseline
- Continuous improvement
- Lean principles
- 3 pillars of Scrum
- Scrum Board
- Waterfall Methodology
- Velocity in Scrum
- What is Definition of Ready
- Lean vs. agile
- Scrumban
- Lean Methodology
- Sprint backlog
- Burn up chart
- 4 kanban principles
- 4 kanban metrics
- Program vs. Project Manager
- Gantt chart examples
- Definition of done
- Backlog grooming
- Lean process improvement
- Backlog refinement meetings
- Scrum values
- Scope of work
- Scrum tools
- Tools
- Workflow automation software
- Templates
- Task tracker
- Workflow automation
- Status report
- Workflow chart
- Project roadmap
- Project schedule
- Tracking software
- Roadmap tools
- Technology roadmap
- Project scheduling software
- Backlog management tools
- Understanding workflow management strategies
- Workflow examples
- Create project roadmap
- Sprint planning tools
- Sprint demo
- Project Timeline Software
- Top task management tools
- Product backlog vs. sprint backlog
- Top workflow management tools
- Project dependencies
- Task dashboard guide
- Sprint cadence
- Fast tracking
Product Management
- Overview
- Product Roadmaps
- Product Manager
- Tips for new product managers
- Roadmaps
- Tips for presenting product roadmaps
- Requirements
- Product analytics
- Product development
- Remote product management
- Minimal viable product
- Product discovery
- Product specification
- Product development strategy
- Product development software
- New product development process
- Product management KPIs
- Net Promoter Score (NPS)
- Product critique
- Prioritization frameworks
- Product features
- Product management tools
- Product Lifecycle Management
- 9 best roadmap software for teams
- Product launch checklist
- Product strategy
- Product engineering
- Product operations
- Portfolio management
- AI and product management
- Growth product management
- Product metrics
- Product release
- Feature request
- Product launch
- Product planning
- Product launch event
- Value Stream Management
- DevOps
Agile tutorials
- Overview
- Jira and Confluence sprint refinement
- How to do scrum with Jira
- Learn kanban with Jira
- Learn how to use Epics in Jira
- Learn how to create an agile board in Jira
- Learn how to use sprints in Jira
- Learn Versions with Jira
- Learn Issues with Jira
- Learn burndown charts with Jira
- Auto-create sub-tasks and update fields in Jira
- How to automatically assign issues with Jira Automation
- How to sync epics stories with Jira Automation
- Automatically escalate overdue issues in Jira
About the Agile Coach
- All articles
Auto-create subtasks with Jira automation
This guide reveals how to create a Jira automation rule that automatically creates sub-tasks when an issue is created.

By Kev Zettler
By Kev Zettler
Kev is a lead full stack web developer and serial entrepreneur with over a decade of experience building products and teams with agile methodologies. He is a passionate contributor, author, and educator on emerging open source technologies like DevOps, cryptocurrency, and VR/AR. In his free time, he participates in indie game development jams.
New Trigger
The first step is to select a trigger from the New trigger selection screen.
Next, find the Issue created trigger from the list of triggers
You can also find the Issue created trigger by searching for it in the search bar. Once you have selected the Issue created trigger, click the Save button.
New Condition
Next we will add a New condition component that will perform an action if the issue type is a Task. Click on the New Condition option on the Add component page.
Next, click the Issue fields condition:
This will direct you to the Issue fields condition configuration page. From the Field drop down, select Issue Type, change the Value to Task, and click the Save button.
New Action
To add an action to the rule, click on the New action item on the Add component page and filter for the Create sub-tasks action. Click the Create sub-tasks item to proceed.
On the Create sub-tasks page add one or more sub-tasks by clicking the Add another sub-task and fill in the Summary fields as you like. You can also configure the fields that you’d like in each sub-task.
When you click Add fields on the third sub-task the other two sub-tasks will be created as a separate action. You will be taken to a new Create Issue screen where you can configure additional fields. Click the Save button when finished.
Turn it on
This brings you to the Add component view where you can name the new Automation. Once you do, click the Turn it on button.
Try it out
Now that you created and activated a new automation rule, it’s time to try it out! Go back to your project, create a new issue, and set the type to Task.
Once you’ve created the new task, the automation rule will activate in the background. You can confirm if the automation rule succeeded by visiting the Audit Log. Navigate to Project Settings -> Automation, find your new Automation rule, and click the Audit Log tab. You should see a view similar to the following:
In the Audit log, if you see a row under the column Status labeled SUCCESS you’ve successfully built the automation rule. If you see the label SOME ERRORS, click on the Show More operations links to debug those errors. As you can see in the screenshot above we had to test and reconfigure our automation rule a few times before we were successful.Â
Once you have confirmed the automation rule operates successfully, return back to your project and you will see the new sub-tasks!
Recommended for you
Templates
Ready-made Jira templates
Browse our library of custom Jira templates for various teams, departments, and workflows.
Product guide
A comprehensive introduction to Jira
Use this step-by-step guide to discover essential features and the best practices to maximize your productivity.
Git Guide
Understanding the Basics of Git
From beginners to advanced experts, use this guide to Git to learn the basics with helpful tutorials and tips.