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
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
I am trying to set an automation when Resolution is set to Done then change the Story ticket status to Done from Closed. I have tried with simple if-when-then logic but our Story workflow doesn't allow status to transition directly from Closed to Done.
Thus I am following the workflow transition i.e. Blocker-->Dev Testing-->PO verification-->Done. But then getting the below error msg, " Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)".
I was able to perform the same sort of automation with the Bug ticket type, but the automation kept throwing errors for Story type. Please advice, if there is a workaround or if i am missing something here. Thank you in advance!
Hi @Bijal Patel
I'd suggest adding a direct transition from "Closed" to "Done" (called 'auto-close' or something) and make sure there's no screens, conditions or validators on that transition.
Alternatively, you could share the existing transition to "done" (from the "closed" status) assuming there's no screens associated with it and/or any conditions or validators are true.
The "Resolution" field should only be set on transition to Close. Hence, use this transition to trigger your rule and then check whether the resolution field is set to "Done". If so, then automation should transition to "Closed".
The following works fine for me...
I hope this helps?
Hi @Bijal Patel
If you can ... try to get your jira admin to add the extra transition then that's the simplest route. You could get them to add a condition on this transition to limit it only the specific user (actor) for the rule - or add a new group in which the actor belongs (e.g. "automation for jira" is usually the default actor?).
However, if you really can't get a change to the workflow - then you'll be forced to go down your original suggested route of moving them through series of transitions ...
It's not very efficient - but I think you may need 4 separate rules - one looking for each of the corresponding transitions and passing onto next one (i.e. allowing you to automatically move tickets in between the 5 statues).
Any conditions or validation used on any of these transitions would also need to be successful as part of the automation. Also, if there's any workflow screens being displayed on any of these transitions then again this may restrict the rule from running.
I hope this helps?
@Mikael Sandberg - I have attached the workflow for your review.
We are using Resolution Jira system field.
Condition formatting is implemented when transitioning to "Closed" status, Popup window shows up for a user to provide a reason for closing the ticket out.
User should only be choosing "Closed" for special cases e.g. Duplicate ticket, Cancelled Requirements, etc.
In our case; User is selecting "Closed" as a ticket status and in the resolution field they are selecting "Done".
What I am trying to do here is : When resolution is Done/fixed/pass/resolved then change the Ticket status to "Done" instead of "Closed"
You said you had a similar automation for bugs that works, correct? And are both bugs and stories using the same workflow? Does the global transition to Blocker have any conditions on it?
What does your workflow looks like? When are you setting the resolution? Normally the resolution is set as part of a transition since that field becomes required when it is added to a screen.