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.
Join now to unlock these features and more
I'm setting up an automation from a Jira Cloud project to a Jira Product Discovery project. The actor of the rule is Automation for Jira. The scope of the project is set to multiple projects (both the Jira Cloud and JPD project), I also tried to use the global scope.
The strange thing here is that automation manages to edit the issue (changing the link) but automation does not manage to assign the issue to a new user - see:
Any ideas on how to fix this? Thanks!
also, is CORD your JPD or JSW project? Have you, or can you create a test automation for CORD that simply checks to see if you can assign an issue? Example... Issue created, Assign issue. This is simply to isolate where the issue may/may not be in current rule.
Hi @Jack Brickey - CORD = JPD project.
I think that I have found the problem, but not the desired solution.
I created a simple automation, like you suggested. The actor of the automation is Automation for Jira and I receive the same error as before. When I change the actor role to myself, the automation is suddenly able to run and executes as expected.
But... I would rather not want my account to be used for this, as it will show up in the history of edits etc. Any ideas on how to solve this permission issue?
You should not have to do that. I have verified in my instance with a JPD project that automation for Jira can be the actor and assign issues. I think the issue lies within the Access settings of your JPD project. Please share your config info.
Hi @Mart Postma , JPD is quite new and as such the behavioral details are still new to me. What is clear is that the underlying permission scheme is much more limited than that of your software. As mentioned by myself and Kseniia it appears that we simply have Creator, Contributor and Administrator roles. What is unclear is where AFJ falls but it seems it is hidden and likely defaults. It absolutely should have the necessary permissions to set the various fields in issues including Assignee. My testing would confirm that. At this point, I'm looking for any possible differences between your environment and mine.
Could you share your rule in JPD when actor is AFJ along with the audit log resulting from triggered rule?
For now, I will log a support ticket to find out what the exact issue is here with the help of the Atlassian team. Will update once I found the solution. Thanks.
Hi @Mart Postma,
Please check if the project role atlassian-addons-project-access has the Assign issues permission. This role is needed for apps to run, including Automation.
This permission is probably missed.
@Mart Postma, sorry, it's my mistake. I confused a Product Discovery project with the Software one.
Looks like all the project permissions are defined on the tab Project settings > Access.
I tried to reproduce your issue and got another error while running a rule with the Create issue action with the Automation for Jira account as the actor:
When I set myself as the actor, there no errors with the same rule configuration. Just like you, I still can’t understand what the problem is...