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
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:
Kind regards,Bill
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.
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?
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.
It looks like you're new here. Sign in or register to get started.
