We have a rule automation rule that triggers on a pull request merge via Github and transitions an issue into new status. I have received two separate errors for this automation.
Error #1 No transitions found for user. Ensure that the rule actor has permission (including issue security levels) to see issue and perform transitions.
I have checked permissions on the project and atlassian-addons-project-access is the rule actor for the github integration and this has 1st class permissions for everything.
I also checked the issue security of which we have not enabled that on our project.
Error #2 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 have no idea what to look for on this one.
I have not been able to get a successfully automation for this rule. I look forward to any help.
Hello @Josh Topel
Thank you for reaching out.
Can you confirm if you are using a Next-gen or Classic project?
The errors returned to you usually happens when the workflow does not allow the current status of your issue to transition to the destination status (AWAITING UAT). In other words, to allow the automation to transition the issue to the status "AWAITING UAT", your workflow must have a transition between the issue status and the destination one.
Please, check the steps below to confirm if the scenario above is matched:
Let us know if the steps above worked for you.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events