Why does Jira->JPD automation fail when actor is Jira Automation?

[Glenn A]

I tired to implement this automation shared by Atlassian's team and it failed seemingly due to access limits:

https://www.loom.com/share/dc391cef278f4e31ba369a53aaa701d7

If I change the actor from Atlassian Automation to myself (I am an org admin) or any user with any level of JPD access, it works. 

I am testing this out on a personal Atlassian instance that is still 'pretty virgin out of the box' in its configuration with a set of users at differing role levels.

What am I missing? What do I need to do to make the Jira Automation user work as the actor?

Thanks!

[Nick Haller · Accepted solution]

Hi @Glenn A ,

We've noticed other customers running into this issue, and it's a minor bug on our end with the A4J user not being granted JPD product access. The workaround for the time being is adjusting the Actor of the rule to a user that has JPD permissions.

Unfortunately the A4J user cannot be granted permission on your end through the admin hub, but JPD support should be able to help further. You can reach out within your JPD under the Give Feedback tab >> Get help from the support team, or opening a ticket HERE.

[Glenn A]

@Nick Haller any updates on this being fixed? The workaround using me as the actor is creating problems. I have an automation that creates a new issue in a Jira project when triggered by a JPD issue. I need the new issue to have the trigger issue's reported as its reporter. If I run it as the actor, I am set as the Jira issue's reporter (I am not the trigger issue's reporter). If I run it as J4A, the reporter in the new issue is correctly set, but the automation actions the cross links (setting a few fields) in the JPD issue fails: 

Unable to find any issue field values to edit:

<trigger issue key>

[Nick Haller]

Hi @Glenn A ,

Apologies for any inconvenience this has caused. There is not much of an update to provide on the fix for this at the moment.

In the meantime, I do believe you should be able to set the reporter on the Jira issue, and copy the idea's reporter to the issue's reporter field.

For example when creating a delivery from an idea, I can configure an automation to set the reporter using something like this, and it'll copy the idea's reported as expected:

[Glenn A]

Hi @Nick Haller

That won't work for me because there isn't a link created in my automation to trigger a subsequent chained rule as you suggest, but that does give me the idea to split the automation and chain them using different triggers... that might work at the cost of doubling our monthly automation count. (a more cynical person might read into why this has a lower fix priority ;) )

Thanks for the thought!!!

[Alex Ortiz]

@Glenn A 

We just tried recreating this rule just the way the Loom has it, and it works as the author being Automation for Jira.  

Any way you can give us a loom/screenshots of your settings/rule?

Check out 25 minute mark on this video to see what we did:

https://www.youtube.com/watch?v=H0mYN-yNDxc

[Glenn A]

@Alex Ortiz, just watched your channel (food for thought: maybe do it as open office hrs and have ppl ask you the question live vs walking the queue) and although I see you got it to work, gotta say "Sorry buddies" right back to you and defer to the expert answer above that it's a bug (Robert had the right idea on the J4A user's scope)