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?
Hi @Sohail Alam,
Try to add the Related issues condition to your rule and specify JQL that matches with sub-tasks:
This condition will prevent creating the second sub-task.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sohail Alam, please send screenshots of your rule and the audit log.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can we add something like, if the task already has a sub task then do not create extra sub task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.