Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation - create tasks under story and not on same level

As each of our stories does need to go through Quality Assurance team, we have setup an automation. 

When a story is created, Jira will also create a QA task. 

Unfortunately it creates the QA task on the same level as the story and they are all treated as child-issues. Which makes the Epic very crowded and we do not see the progress of the story.

We would like to have the QA task under the story. The same applies for other tasks und the story, but I assume the solution will apply also to them. 

The question is, how can I create this type of automation and relationship? 

Bildschirmfoto 2022-09-01 um 14.30.41.pngBildschirmfoto 2022-09-01 um 14.32.23.png

2 answers

2 accepted

1 vote
Answer accepted

Hi @Michael Hauschild,

For the QA task to be a child issue, you need it to be a subtask issue type. In the example below I have created a QA issue type that is a subtask:


You can then create QA subtasks through Automation:


Depending on your configuration, you may also not want to create a dedicated subtask for QA tasks and just use classic subtasks:


Hope this helps,

- Manon

0 votes
Answer accepted
Elvir Rising Star Sep 01, 2022


I suggest not to copy the epic link fron the story so that the QA Task will not show up in the epic view as child issues.

The QA Task are need to be linked to the stories. You can have them on the same board as stories or created a decidated board for the QA team.


The other solution is to create a issue-type QA task but as a sub-task. So that QA tasks will show under stories as sub-tasks.


Best regards,

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events