Sub-tasks status dependent on another sub-task

[Julliane Chan]

Hi, 

Not sure if this will come off as confusing, but I created an automation that upon ticket creation 6 sub-tasks will be created, the requester requires that the 5 sub-tasks will not be able to change status until the first sub-task requirement is provided, (or at least what I'm thinking is once the status of the first sub-task has been set to DONE)

Is it possible to block the status transition of the 5 sub-tasks?

[John Funk]

Hi Julliane,

Not sure that I completely follow, but maybe create a custom field that is hidden from the user. When the issues are created, set the field to a certain value. Then add a Condition in your workflow to not allow the issue to transition if that field has that value. 

Then create another automation rule that fires when something happens with the first sub-task (that doesn't have a value for the hidden field). Whatever that is that should free up the other work items will be your trigger. Then add an action to the automation that clears the value of the hidden field.  This will then allow it to move forward. 

[Julliane Chan]

 Hi  @John Funk 

I have done the following steps 

1. added a custom field 

2. added a pre-set value of "FALSE" in the custom field created. 

3. The first sub-task has no Value set for the custom field 

4. Added condition to the workflow that the status should only be allowed to transition if the value of the custom field is NULL 

(The trigger to set the custom field of the other sub-tasks to NULL would be the status of the first sub-task when it is transitioned to DONE)

Should I create a new automation that would trigger the custom field to update to NULL, or can I just add it to my existing automation?

Should I create a new FOR EACH branch or should I add it under per sub-task rule? 

 

[John Funk]

You will need a new rule for when the first sub-task transitions to Done to update all of the siblings. 

[Julliane Chan]

Hi @John Funk

Thank you for answering, i tried creating the new rule, the question is how I identify the sibling subtasks of the first subtask from the new rule. I tried using the Link issue but i can't use issue key of the sibling subtasks, since it will dynamically change and it's a new rule.