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

Adding / duplicating subtasks (Automation for Jira)

Hi there!


Is it possible to block duplication of subtasks within the parent issue when changing its status backward / forward? Please have a look at the below;


When: Issue Transitioned
From: Draft
To: In Review

Then: Create a new (sub-tasks)
In: My_Project

However, once I get back from step "In Review" to "Draft" and then again from "Draft" to "In Review" - subtasks duplicate and arise again.


I hope that the solution is pretty easy for advanced users and I can count on your help. :)



1 answer

1 accepted

1 vote
Answer accepted

Hi @Matthew Burrel 

If I've understood what you're looking for here then adding a condition like this should work for you:


Great - it works! Thanks for a swift reply :)


Like Stuart Capel - London likes this

@Stuart Capel - Londonwhat if.. we have a previous transition with a sub-task creation and the second one I mentioned above? In this scenario, one auto-created sub-task in the first transition blocks creating another sub-task in the second one. 







All in all, once we have auto-created sub-task between "TO DO" - "Draft" transition - Another sub-task in further "Draft" - "In Review" transition is not created. Any idea? :)




Hi @Matthew Burrel 

I'm not completely clear on your question here. Do you mean why doesn't the automation create sub tasks when transitioning from 'Draft' to 'In Review' in 2nd?

Or are you asking if there's a way to stop duplicate sub tasks being created, only if the issue has already transitioned from Draft to interview once before?

Hi @Stuart Capel - London

Thank you very much for your commitment.

Both, because previously by those 2 rules (When: Issue Transitioned) I auto-created subtask(s) per each step (1st step - From "To Do" to "Draft", 2nd step - From "Draft" to "In Review"). It worked nicely at that time. However, the first issue was raised when I start changing the mentioned statuses backward / forward - then subtask(s) duplications popped up. Then I got your advice to add in the rule "When:Issue Transitioned" from "Draft" to "In Review" this part - > "If: Sub-tasks not present". I added this item in the second rule and now after creating subtask(s) in the 1st step (From "To Do" to "Draft") - the system stopped adding subtask(s) in the 2nd step.

I hope that is clear right now and not so complicated as it seems. ;)


@Stuart Capel - Londonany ideas? you are my last hope :)


🙂 I had a look last night but I need work out the jql. Bare with me, I might have what you need 👍

Like Matthew Burrel likes this

Hi @Stuart Capel - London any chance to get an update here? I believe that you came up with some fresh ideas :)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events