a new subtask should be created automatically when multiple subtasks are DONE.

[Caleb Park]

Hi guys,

My workflow system is like the following:

1. When a Story is created, a sub-task A is automatically created.

2. When the sub-task A is marked as DONE, two new sub-tasks B and C are automatically created under that Story.

3. When BOTH of those two sub-tasks B and C are marked as DONE, another new sub-task D should be automatically created under the same Story.

 4. The sub-task D is marked as DONE as the last step.

So, the step 3 above is where I get stuck at. 

Both of those two sub-tasks B and C MUST be DONE to get the next new sub-task. If only one of those two sub-tasks is done, new sub-task should not be created.

NOTE: I don't want to use a method of: scanning all sub-tasks DONE and triggering the automation to create a new sub-task D because this will cause a problem when all the sub-tasks A, B, C, and D are DONE at the end of the process, this method will also create another sub-task E.

I would appreciate snapshots of automation workflow so that it would be much better to understand!

Thank you so much in advance.

[John Funk]

Hi Kyung,

You would need to identify Sub-tasks B and C somehow - probably with a custom field. The field can be hidden from the user, but you would need to use the value for a condition check.

Or another solution might be to create a different Sub-task issue type then you could do your condition based on the issue type. But that will only work with Company-managed projects as Team-managed projects don't currently allow you to create multiple Sub-task issue types. 

[Caleb Park]

Hi John,

Thank you for your answer.

So, I don’t think the second solution will work since it’s Team-managed projects (I guess). Therefore, I feel like I should stick with the first solution working with Custom Field for Condition Check. Can you please tell me more about  the first solution then?
Snapshots would be great, if you can’t take snapshots, more details would be good too. Also, if it’s hidden from the user, how can I find that field?

Thank you so much for your help, John.

[John Funk]

First, when I say hidden - I just mean that it is not included on the screen. It would be populated by an Automation for Jira rule so you wouldn't need access to it on a screen. Just populate the field with a value when you create the issue using your automation rule. 

Then use the value of the field in a condition when you are checking if B and C are done. 

[Caleb Park]

Hi John,

Honestly, it is difficult to implement your answer to the actual automations. Can you please post something like Automation Workflow? Or can you be more specific with more details for each step?

[John Funk]

Can you share the rule that you have so far? Then we can go from there. 

Also, you could go ahead and create the custom field - whatever type you would like - and just not associate it with a screen. 

[Caleb Park]

This is just an example of my current Automation (Not exactly the same to my automation, but its concept is just the same).

So, the concept is this:

A new subtask C (Label is Security) should be created after BOTH of subtasks A and B (A is when Label is "Infrastructure" and B is when Label is "Automation") are DONE.

I couldn't figure out how to make it work without adding another qualification that is regarding "When all sub-tasks under a Story DONE".

Therefore, according to my current automation, for instance, when only "Infrastructure" is DONE, the automation thankfully does not get triggered because all subtasks are not DONE yet since "Automation" is not DONE. 

I know this algorithm works, but I am wondering if there is any other way to make it work without "When all sub-tasks under a Story DONE" concept, for example, it could be done with using condition function or something.

[John Funk]

I think what you have is correct. Is it working? Or not working? Have you tested all scenarios? 

[Caleb Park]

No, that system didn’t work properly. But after putting the last step “Create a new issue” into the “For Parent”, it works well.

[John Funk]

Great! So it is working now? 

[Caleb Park]

Yes, Sir. Thanks for your time!

[Josué Garcia]

This is an interesting workflow. A far as I know, you can only 'for' loop through all the sub-tasks and it really and all or nothing deal. I would play around with making another a duplicate sub-task type then keying off of that to check if B and C are done?

[Caleb Park]

Hey,

I have already played around with several options, but it never worked. I feel like it is not possible to do this work in one automation step.

I want to wait for more replies under this question!

Thanks, Josue.