Create tasks that populate with subtask only one epic

[Nimantha Deshappriya Kappetiyagoda Vithanage]

Hello, 

I’m planning to create tasks that automatically include multiple subtasks, but I only want this to apply to a specific epic. How can I set this up?

[Viktoriia Golovtseva _TitanApps_]

Hey @Nimantha Deshappriya Kappetiyagoda Vithanage welcome to the community.

You can achieve this in Jira using native automation rules.

To create tasks (issues) that automatically include subtasks (keep in mind that tasks should belong to specific epic) you can:

1. Go to Project Settings → Automation

2. Create a new rule with:

   • Trigger: “Issue Created”

   • Condition: “Issue fields condition”
     → Field: Epic Link
     → Condition: equals
     → Value: Your specific Epic key (e.g., EPIC-123)

   • Action: “Create sub-tasks”
     → Add the subtasks you want to generate under that issue.

This way, only issues linked to your target Epic will trigger the subtask creation. Please check the Atlassian documentation for details and specific use cases.

Tip: Make sure the issue type supports subtasks and you’ve set up the appropriate issue type scheme.

If you want a faster, reusable, and more scalable solution, I would recommend as the representative of the company to check out Smart Templates for Jira by TitanApps:

• Predefine template structures (e.g. 1 task + 5 subtasks)

• Automatically apply the template based on issue type, project, or custom field values (like Epic)

• Integrate with Jira Automation to trigger templates when issues are created or transitioned

Example: You can set up a rule that applies a “UX Design Task” template whenever a story is created under EPIC-123, instantly creating all the subtasks in one go.

[Akhand Pratap Singh]

Hello @Nimantha Deshappriya Kappetiyagoda Vithanage ,

Good Day, Welcome to Atlassian Community.

From your rule, remove the first condition "if: work item matches JQL", rather use another condition called related "Related work items condition".

If it is a specific Epic, then you can directly use Key of the epic in that JQL, or if there is some other condition you can update the JQL Accordingly.