Jira Automation - Transition Issue not working with Automation for Jira actor

[Christopher Mundt]

I am in a company-managed project.  I have a workflow that works when the actor is me, but fails when the actor is "Automation for Jira".  When I look at the Permissions I see that atlassian-addons-project-access is assigned to Transition Issues.  My role has permissions of Administrator (project), Developer, Manager, Requirement Owner, and User

[Bill Sheboy]

Hi @Christopher Mundt -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

• what type of project is this (e.g., company-managed, team-managed, etc.), 
• an image of your complete automation rule in a single image for continuity,
• images of any relevant actions / conditions / branches,
• an image of the audit log details showing the rule execution,
• an image of your workflow transition that is not working, and
• explain what is not working as expected and why you believe that to be the case.

Kind regards,
Bill

[Christopher Mundt]

Thanks for the guidance.  I've included your suggestions.  Please let me know what other information I might provide to help.  Given the fact that it works for my ID I would assume the Automation for Jira 'user' is missing a permission, but I'm not aware of what that would be.

[Bill Sheboy]

Thanks for that information, Christopher.

Are you certain the project is company-managed?  Perhaps confirm that by viewing it in the project list: from the top navigation Projects > View All Projects.

What is the purpose of the Re-fetch Issue action in your rule?

If you review the workflow for the issue type shown in the log (ER-9519) are there any rules / conditions on the transition to "In Progress"?

What problem is this rule solving?  That is, why have manually triggered rule which transitions an issue to "In Progress" when they could just be transitioned by editing the issue or dragging it on the board?

[Christopher Mundt]

Thanks Bill.  The project is company-managed.  My original workflow was much more complex and involved multiple clones as well as linking issues (as well as setting the clones to a status of Blocked).  I wanted to develop this workflow as a test to isolate my issue.  The re-fetch actually serves no purpose in this case and after removing it, I can confirm that the issue remains the same.  There are no conditions to the transition and I can confirm that our workflow allows transition from any state to any state.

[Bill Sheboy]

That is curious...

The error shown seems to indicate the issue is either trying to transition to "New" (which is the temporary condition when an issue is first created from nothing), or someone actually created a status named "New" (which is being confused by the rule's action).

What version of Jira are you using: Cloud, Server, or Data Center?  The rule detail's image does not look like Jira Cloud.

Let's try this: rules can sometimes get "glitched" behind the scenes due to repeated edit / publish cycles, breaking something in the stored JSON.  The way to test for that is:

• Disable your rule, wait a couple of minutes, re-enable it and run it again.  If it still fails...
• Disable your rule, and re-create it from scratch.  Then test the new rule.

[Christopher Mundt]

We're using  cloud.  I've done the couple of items you've suggested.  I'm thinking that next I'll try to transition from a state other than New in case (as you've suggested) maybe it's getting confused.  I'll post tomorrow.  Thanks for the continued help Bill

[Christopher Mundt]

I can confirm that moving between other statuses doesn't work either with the Automation for Jira user.  I guess that makes sense as the workflow should be valid/ok since it works using myself as the Actor

[Bill Sheboy]

At this point, I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/

They may see something we are missing, perhaps in their internal logging.  When you hear back from them, please post what you learn.  Thanks!

[Christopher Mundt]

Thanks much.  This is for a client, but I'll see what I can do to get a ticket in.  If I'm successful I'll be happy to post an update.