Help Required for one of the Automation Rule!

[Vijay Kumar]

Hi,

I am creating an Automation Rule for the below requirement.
Requirement:
Whenever a User Story, Defect, Task status is changed to 'COMPLETED'. I need to update the Subtasks underneath that story, defect & tasks are also marked as 'COMPLETED.

I created the rule, but it is throwing me an error for the required action.

I have attached rules details in a screenshot, also the 'Audit Log'. Please refer to that and let me know, you have any solution for this.

[Bill Sheboy · Accepted solution]

Hi @Vijay Kumar 

The way you rule is written, it will halt on the first condition not met.  Please remove two of the conditions, and change the first one to this:

• Issue Fields Condition:
  • field: issue type
  • condition: is one of
  • value: select Story, Defect, and Task

And inside of the branch, you may want to add a condition so the Subtask does not transition when it is already Completed.

Kind regards,
Bill

[Vijay Kumar]

@Bill Sheboy 

Thank you so much for the reply. Its really helpful.

Now it started working, however it failed because of some other reason. Whenever we are closing a Subtasks, we need to update the 'Resolution' field as 'Done'. We have one step in between. Because of this, for one of the sub-tasks it couldn't update.
Is there a way we can override this step? or can ignore?
Also, i am not sure about 'how to add a condition, so that Subtasks does not transition when its already completed. Please suggest on this as well. 

[Mikael Sandberg]

So before doing the transition of the sub task, add an Edit issue action that sets the Resolution field.

[Bill Sheboy]

Or, in the Transition Issue action, select and set the Resolution at the same time.

[Vijay Kumar]

@Bill Sheboy @Mikael Sandberg  Hmm...lemme try & get back to you guys!

[Vijay Kumar]

@Bill Sheboy @Mikael Sandberg 

You both are incredible! Thank you so much for your help. You have no idea how much this means to me and how much time it saves. Thanks again, and I hope you have a fantastic rest of your day!

[Mikael Sandberg · Accepted solution]

Is the work item that you are using a story? The way your automation is configured it will only run if the work item is a story, and then it will stop on the next condition because a work item can only be one type. Since you want it to run on different work item types you need to use the IF/ELSE condition and the OR option in it.

[Vijay Kumar]

@Mikael Sandberg  Thanks much for the reply. 
I need to run this rule not just on the Story, i want it for Defect & Tasks as well.

I tried look for IF/ELSE condition and OR operator. I couldn't get it. Where do i add these conditions?

[Mikael Sandberg]

You are on the right track. In the IF/ELSE, pick the Issue field condition, select the Issue type field, leave the condition as equals and then in the value dropdown pick the work item type.

It should looks something like this:

You could also pick "is one of" in the condition, that will turn the value dropdown into a multi-select so you can pick all the work item type the automation should trigger on instead of using the "At least one condition matches" option.

[Mikael Sandberg]

The alternative would look like this if you do not want to use the IF/ELSE:

[Vijay Kumar]

Thank you, @Mikael Sandberg I used field condition as per Bill's suggestion and it seems to start working. However, i faced one other issue. I replied to Bill on that. If you have any idea on that, please let me know.