You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi! I am looking for the automation steps for this ask above:
Further context:
Thank you!
If you go to Project settings > Automation and look under Library there is a rule called "When all stories are completed → then close epic" that you can use as a starting point, just change the statuses to fit both of your use cases.
Hi @Mikael Sandberg thank you so much! I am having an issue with the in-progress part of this now? It is rejecting my JQL. Could you take a look?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg I actually just tried this and it didn't trigger anything for my epic. I am not sure what I did wrong as I copied the rule exactly. In the audit log it says "no actions performed"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your JQL is missing status = "In progress", using just = "In progress" is not a valid JQL.
When you did the test, did you move a story/task to completed or an epic?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahh, sorry not familiar with JQL. TY!
For the test -- I created an epic and linked task issue
Since there are two work flows (one for epic and one for task) -- I moved the task issue to completed.
The epic remained in "back log" after moving the child issue @Mikael Sandberg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, so try this. On the initial trigger component try and change the status it triggers on, I have noticed that if you use a rule from the library you have to change the default settings for the automation to trigger correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wasn't able to locate the rule for some reason, so I built it out using the screenshot you initially provided. Do you think this still applies/is creating the issue? @Mikael Sandberg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, if you create it from scratch you should be good. If you still have an issue with the trigger not running and the audit log is saying "no actions performed" then you should start there. You could add a log action after the initial trigger to see if it gets to that component.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg I just watched this video: https://www.youtube.com/watch?v=Y5u_i9z06zg
And it seems like the way its set up is doing the inverse? I.e when epic is moved to completed, it moves all child issues to completed? Vs , I want to epic to move to completed when all child issues are done?
The one epic is dependent on all child issues to be complete
Child issues must all equal = completed before the epic can move to completed
Since the child issues all happen at different times, some could be completed before others, but again -- the epic should not move to the complete status until all child issues are done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The example I posted above should only transition the epic if all stories/tasks in it are in the done/completed status, that is what the second condition in the epic branch is checking, the "And: Stories (or other issues in this Epic)" part.
The video that you found is indeed showing the inverse when the epic is moved to done then move all children too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg I deleted and re-did the rule and it finally worked. Thank you for your help!
What I need help with now (promise I am almost done) --
For the epic workflow there is only three statuses: backlog, in progress, completed. We have now finished the automation for syncing with completed.
For the task work flow there is the following in-progress statuses:
* In-progress
* Edits needed
* ready for review
I'd like for the Epic task to recognize that if it's child issues are in one of these statuses, it should remain in "in progress" on its own workflow. I've attached what I tried to do, but it didn't work. Additionally, I think I may need or statements for JQL but am unsure how to do that? please let me know if my thinking is correct, or if I need to make updates.
thank you again for your patience/help
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.
Something like this should do the trick:
In this case I have added a condition to only look for Stories or Tasks that are transitioning, and then transition the epic only if it is on the To Do status. Because you want to move the epic when the first story/task is transitioned there is not need to check that stories/tasks within the epic is in a specific status.
For you I would just add the other statuses that you have for stories/tasks to the initial trigger, assuming that you can move to any of them from any of the other statuses.
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.
On the Epic branch, change the condition that checks the status, because the way you have it configured right now the epic would have to be status = In Progress in order to transition it 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.
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.