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
We have an automation rule that checks after any transition if the new status is "Reopened" and is so trigger the transition of the linked issue (from another project) to "To Do"
Actor is a jira user with the permission to edit and transition issues.
The automation fails with error "No transitions found for user. Ensure that the rule actor has permission (including issue security levels) to see issue and perform transitions."
Can you help me?
I received a prompt reply from the developers after asking for support:
"... I have an inkling it may be a recent bug (AUT-1073).
In short, when Jira creates an issue, it is often too quick for its own good. So it is created with bits of information missing. With automation for Jira, we usually put a small delay in to allow Jira time to populate the issue correctly. The bug above is as a result of this.
If this is the case - there is a workaround until we fix this bug. You could insert a 'refetch issue data' action immediately after the trigger. In 'more options' you can manually configure a delay which would solve your problem."
hey @Henno Gous , thanks for posting this!
I've tried this on my end, and it's still not working (same errors as above).
- I set up the automation to delay for 5 seconds, and then try again. It still didn't transition the issue.
- I added three other fetch rules, just to make sure it wasn't going too fast. (our data center instance is huge, and it's a little slow)
Any other potential things I might be able to do?
We had an indexing problem occur in JIRA yesterday. Users were creating duplicate tickets whilst this problem was going on. Some of the duplicate tickets we are able to transition, some of them we cannot (even though they're in the same status and running the same workflow!).
We cannot bulk update the issue in JIRA as it says we cannot transition the issue.
Putting an automation in place in Automation for JIRA gives the error above. So this can be a result of JIRA buggering up an index I think.
Perhaps the transition you are trying to trigger has some conditions that prevent it from being triggered?