Not creating a ticket when the parent ticket is moved from Done to in progress and back to done

Sohail Alam August 9, 2023

I have an automation rule:

- When a ticket ABC is moved from In progress to Done then it automatically creates a sub-task DEF

-But again if I have to opent the ticket ABC and move it to In Progress and later change it to done, then it will create another sub task DEF, which makes 2 DEF sub task.

Can anyone please suggest automation rule?

2 answers

1 vote
Kseniia Trushnikova
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 9, 2023

Hi @Sohail Alam,

Try to add the Related issues condition to your rule and specify JQL that matches with sub-tasks:Related issues condition Example.png

This condition will prevent creating the second sub-task.

Sohail Alam August 9, 2023

I am confused, I tried doing that but did not work. If you do not mind, could you please share the automation rule?

Thank you

Sohail Alam August 9, 2023

What could be the best automation rule for this? @Kseniia Trushnikova 

Kseniia Trushnikova
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 9, 2023

@Sohail Alam, here's the example:

Rule Example.png

You can update the condition JQL to the more suitable one.

Sohail Alam August 9, 2023

I tried that before but it did not work.

Created a testing task ABC, then move it to DONE. After the ABC gets moved to DONE, it creates a sub-tasks TESTING which is in TO-DO state. But if we find out that ABC was not done completely and then move it back to To-Do and then complete and move it back to DONE then it creates another sub-tasks TESTING, by which we will have 2 sub-tasks testing for one task ABC.

Kseniia Trushnikova
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 9, 2023

@Sohail Alam, please send screenshots of your rule and the audit log.

Sohail Alam August 9, 2023

Rules.png

Sohail Alam August 9, 2023

As you can see, TEST tasks was moved to done first and created ABC subtasks, then it moved again to IN progress and later moved to DONE which created another sub-tasks ABC. And this is the new automation rule that I created

Kseniia Trushnikova
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 9, 2023

@Sohail Alam, it looks like you've posted the wrong screenshot.

This rule doesn't create any sub-tasks. It doesn't really do anything other than check if the task has sub-tasks.

Sohail Alam August 9, 2023

Can we add something like, if the task already has a sub task then do not create extra sub task.

0 votes
David Blank
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 10, 2023

Hi @Sohail Alam ! I wonder if we solved this in your earlier question linked here: Link 

where the answer was to add a condition that checks if Subtasks exist before creating one?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events