I am trying to create issues not in the Parking Lot. Workinng for a start up, I often recieve ideas which we need to begin next sprint, hence I would like to create the ideas in the "next sprint" status.
I have a custom field, called "Roadmap" which one-for-one aligns with my status. I have this so that I can color-code my cards. It seems like I cannot color code statuses.
I then wrote automation, when an idea is created, if roadmap equals "Next Sprint", then transition the status to Next Sprint.
This automation never works, it always turns up with this transition issue:
As depicted above, I've tried turning on the regex button but that doesn't seem to solve the issue.
Hello, Good day. You are manually able to transition the issue ?
Also make sure that there is no condition in the workflow transition.
Also try only the transition to next status without any further actions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I can manually transition the issue from any status to any status. The automation only looks at the "Roadmap" field and transitions the issue, there are no further actions in the automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From the screenshot that you have shared above, I see that you have selected "transition match". Could you try disabling this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi. I just tried disabling it and I am still experiencing the same issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks. There are chances that the automation user does not have transition permission. Could you try changing the automation rule actor to your name/account and check ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That worked and I feel silly. I have many other automation where I remembered to update the actor, I just missed this set of rules. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Donni Shimanovich -- Welcome to the Atlassian Community!
There is a known, racetrack error with the Issue Created trigger. That is, the trigger can fire so quickly some issue data is not available to the rule yet. This often leads to missing data and unusual rule errors. I wonder if what you are observing is a case of this defect.
The fix for that is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit and re-load the data before proceeding.
Perhaps try adding that action after the trigger to observe if it helps with the issue transition.
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.
Earning the Mindful Member badge proves you know how to lead with kindness, plus it enters you into a giveaway for exclusive Atlassian swag. Take the quiz, grab the badge, and comment on our announcement article to spread the good vibes!
Start here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.