nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Assign issue error in automation rule

Mart Postma

Hi,

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!

Accepted answers

All comments

Jack Brickey

did you check the Assign issues permissions in CORD project?

Jack Brickey

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.

Mart Postma

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?

Kseniia Trushnikova

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.

Jack Brickey

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.

Mart Postma

Hi @Kseniia Trushnikova - where can I find this setting specifically for the JPD project?

Kseniia Trushnikova

@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:

Screenshot 2023-11-15 at 18.09.31.png

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...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud