Hi, am trying to create an automation Rule for when any chid Story of an Epic is moved to "In progress" Status, the Epic status gets updated to "In progress" automatically.
Sharing the rule in screenshot I wrote so far which is failing at 2nd condition when i look at the Audit logs.
The first screenshot shows my Rule and 2nd shows the Audit log where it condition did not match the condition. Even though the child story was moved to " In Progress" .
I am not sure where my rule is breaking to update the Epic Status. Am i missing any step here?
Hello @Anu
The second condition you added, under the branch, is trying to apply the condition to the issue that triggered the rule. The conditions applies only to Epics, and the issue that triggered the rule is not an Epic, so the condition does not pass.
What are you trying to accomplish with adding that condition to your rule?
Sorry about that, I shared the wrong screenshot, my bad.
I am trying to check if any child Story of an Epic is "in Progress" status, the Epic status is also changed to "In Progress"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anu
Given what you describe, perhaps you do not need that specific condition on other stories: when the rule triggers and the branch gets to the epic, you know you want the epic in progress also.
Instead should there be a condition so the epic is only transitioned to in progress if it is not already in progress?
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I am at very basics of Jira automation so was trying only one scenario where an EPic is created in To do Status, has 5 child User Stories also in To do status.
when one of the Story is moved to " In Progress", Epic's status automatically updates to " In progress" and same am trying with the Rule in screenshot below.
Once, i get comfortable with first rule, I will add other rules. Hope I was able to clarify my scenario.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Anu
You must remove the "If: Stories (or other issues in this Epic) present" condition. Your rule will not work with that present.
You don't need to check if any of the Epic's child issues are in an In Progress status. The fact that the rule was triggered proves that to be true already. Your rule is only triggered when an issue is moved to In Progress, and will only proceed to update that issue's parent Epic, if it has one.
@Bill Sheboy 's suggestion was to add a condition to check that the Epic status is not equal to In Progress. If the Epic status is not equal to In Progress then transition the Epic to In Progress. You need to change your "Status equals In Progress" condition to use the "not equals" option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
.. deleting due to incorrect
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you both Trudy and Bill.
I was able to make updates and run the automation Rule successfully.
Based on my understanding of this, was able to construct rule to Mark Epic as Done when all child items are completed. Appreciate the time taken to explain.
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.
Hi @Trudy Claspill & @Bill Sheboy
As mentioned above I created the Automation rule as below
But it throws an errors as below
As mentioned the Epic status get transitioned to In progress as shown below
How to rectify this error?
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.