Transition Parent with resolved and unresolved Sub-tasks

[Shawn Kaowili]

Hi, Here is my scenario:

Parent Issue has multiple Sub-tasks

DEV: Implement Code
DEV: Unit Test
QA: Create/Update test Cases
QA: Execute Test Cases

Currently, my transition works like this:

When one of the DEV Sub-tasks are moved to DEV In Progress, Parent transitions from Defined/Open to "Dev In Progress.

When both DEV Sub-Tasks are set to Complete, Parent Transitions to QA and Notifies QA Team that Parent Issue is ready for Testing.

When Both QA Tasks are Completed, Parent Transitions to "Ready For Review/Demo

Here is my issue, when one of the Test Engineers, Moves Creates/Updates Test Cases to Complete Prior to Dev being started/completed the Parent transitions to Ready to Review/Demo, when this happens, I manually move Parent back to correct Status.

Anyone know how, I can stop transition to "Ready For Review/Demo" unless all Sub-Tasks are set to Complete .

Here are my transition rules.

Thanks in Advance

[Bill Sheboy]

Hi @Shawn Kaowili 

First thing: I suggest a team conversation to learn if the scenario you are describing (moving QA items before DEV items are completed) is valid.  There may be a larger team process concern beyond the scope of the automation rules.  Understanding that will help to know how to improve.

After that...from what you have described and shown in your rules, what do you think of just adding another condition to your third rule to check the progress of the DEV subtask?  That would prevent changing the parent.

Kind regards,
Bill

[Shawn Kaowili]

@Bill Sheboythanks for your response. The conversation isn't necessary as we do some time tracking and they need to track the time to create/update test case design. I will try and add another condition, any suggestions on what that condition should look like?

Thanks Again,

Shawn

[Bill Sheboy]

Shawn, in your rule which is just checking for the changes to QA subtasks, what are you trying to detect? 

For example, you noted not to proceed if the DEV subtasks were still not started or in progress.  So perhaps add a separate condition for that after your QA subtask checks.