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
Hello everyone,
First of all I would like to know if what I'm trying to do is feasible with Jira project automation.
Use case: Having a story with a number of sub-tasks (i.e. child issues) I would like to automate the transition of the Story (i.e. parent issue) when all sub-tasks with Design component for example are move to Done i.e. when all orange sub-tasks (or last orange) are moved to Done. Is this possible? If yes, how can I manage this?
So far I know how to move my story for example to Design as soon as the first sub-task moves to In Progress. I also know how to move my story when all sub-tasks moved to Done. What I cannot figure out is how to transition my story when a sub-set of my sub-tasks is moved to Done.
Thank you in advance,
George
Hi @George Stamos ,
Do the subtasks have the field "Component" filled with component "Design"? Or is color the only way the are detected as Design issues?
Best
Stefan
In case there is a component "Design" in the SubTasks the following rule should do the work as expected:
Looking forward to your feedback.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Color coding was for the sketch :). It is component as you thought so. I forgot to mention I'm on a data center not cloud though :(.
I'll give it a try to see if i understood correct and let you know.
Thank you for sharing Stefan Salzl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks for the information. That‘s a game changer as the lookupIssue action is not available for data center 🙈
need to rethink the solution 🤔
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Stefan Salzl any ideas are more than welcome. Its been two days now I cannot take this out of my mind 🤯
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh man I feel you. This is nerve wrecking 🙈🙈🤣🤣
I‘ll give it another shot today 🙌🏼
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My use case is related to Kanban and metrics I get from Stories (i.e. cycle time in status) so I don't want to forget them as they will mess-up my metrics but it seems I will have to do a manual check on a daily basis to have realistic metrics.
So, for the moment not knowing if this is possible or not, it really keeps me awake in the night :) 🤯
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hmm.....got your point and why this keeps you awake at night 🙈
Would it be sufficient if this action runs once or twice a day? The rule could then start with a JQL that checks stories.
Otherwise I guess a workaround for the lookupIssue could be a webhook to JIRA API in the automation rule.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think this the issue, even what you describe is not possible or still i didn't figure out how to do it.
Keeping me up in the night :) it is just me getting frustrated not being able to solve this riddle which actually looked simple in the beginning.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Guess I found a solution. tbh: it´s not the simplest one but in my tests it worked.
see screenshot:
Hope this helps (and brings back some more hours of sleep 😉🙌),
Looking forward to your feedback.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There may be another way to do this with Server/Data Center that does not require the web request / REST API call is with delegation:
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.
@Bill Sheboy omg.....THIS seems quite a lot easier than my solution 🙈💪
Anyways it was quite a big journey of learning new things and "getting familiar" with API calls 😊
Thanks for your valuable hint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Stefan Salzl ,
I did implement your proposal above and got an error 500.
Didn't have the time to trouble shoot though. I will check tomorrow but maybe I start with @Bill Sheboy proposal 😉
I will let you know and share the results here. Thank you both
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would you please clarify something about your use case? That may help the community to offer you suggestions to help.
You describe a need to move the parent story to "done" when a subset of the child subtasks (e.g. the orange ones in your picture) are all "done".
What work do the "blue" subtasks represent that they do not also need to complete for the story to be considered complete? For example, are they optional and so are abandoned when the "orange" ones are all completed?
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.
Hello @Bill Sheboy ,
As shown in the picture, I want to move my story I.e. parent to the next flow step when a subset of my sub-tasks is moved to done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks and I understood that from your picture.
I was asking: why would the other subtasks not need to also finish before marking the story as "done"?
Is your intention work would continue on the other subtasks even though the story is marked as "done"? If so, measuring what you describe as cycle time would be inaccurate as it misses some of the working time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Moving design sub-tasks to done would mean according to our policy for example that design phase is concluded meaning our story need to move to the next flow step. Same if blue ones move to done then another flow step will follow for the story etc.
To be honest I never mentioned I want to move the story to done. This will happen only if all sub-tasks are moved to done.
Hence there is metrics as you assume correct that Measure lead time as well from To do to done.
Nevertheless this is not what is this thread is about 🙂, thank you for asking
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, that helps! I misunderstood the language in your question to mean moving the story to "done", not just to transition it for the "in progress" steps.
In that case, @Stefan Salzl has you on a good track with using Lookup Issues with JQL and checking {{lookupIssues.size|0}} to determine when all of the relevant subtasks have progressed to move the parent.
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.
Hello @Sachin Dhamale ,
Thank you for sharing!
Unfortunately this doesn't fall to the case I'm after.
It doesn't work for me
Best regards,
George
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.