Jira automation: assign user does not work with pull request trigger

[James Phan]

I am trying to create an automation that assigns a user to an issue when a Pull Request is created, however, all the ways I tried so far leaves the user as Unassigned even though in the audit log, it shows that the automation was successful.

What's strange is that if I change the trigger to be Manual, then the assignment works. I've listed so far the various ways to assign the user below.

Option 1: Using the Assign User action [set it as User who triggered the event]

Option 2: Using the Edit Issue action [set it as User who triggered the event]

Option 3: Same as Option 2, but [set it as {{ initiator.accountID }}]

[James Phan]

.

[James Phan]

The audit log reports that the issue was edited successfully. Screenshot below is one where I had both the Assign issue and Edit issue actions enabled. Can see that the log shows it was ran without issue, but looking at the history within the ticket, no changes were made

Edit: disregard, meant to use this as a reply to another message

[Trudy Claspill]

Hello @James Phan 

Welcome to the Atlassian community.

What is the output in the rule execution Audit Log for each of these attempts?

If you use the Log action to print the {{initiator.accountID}} smart value into the Audit Log during rule execution, what value do you get?

[James Phan]

The audit log reports that the issue was edited successfully. Screenshot below is one where I had both the Assign issue and Edit issue actions enabled. Can see that the log shows it was ran without issue, but looking at the history within the ticket, no changes were made

Using the log action, it doesnt return a value. In the action, my input is: This is a message: {{initiator.accountId}}. You can see the output doesn't return the expected account

[Bill Sheboy]

Hi @James Phan and @Trudy Claspill 

That is curious...I would have expected the initiator to either be the Automation for Jira user or the person who created the PR.

I did find this defect indicating if a user does not have an email address in their public profile for Github matching their Jira profile, no match is possible for the PR actions.  Does that match your scenario?

https://jira.atlassian.com/browse/JSWCLOUD-23906

Kind regards,
Bill

[James Phan]

Unfortunately, even changing my Github email to match that of my Jira profile and having it public does not fix the issue.

In fact, this is what I see in the logs when running the automation again. 

[Bill Sheboy]

Sorry, I am out of ideas to try.  Unless Trudy has more, I recommend working with your site admin to submit a support ticket to Atlassian for this one.  You appear to be on a Standard license and so the admin can do that here: https://support.atlassian.com/contact/#/

When you hear back from them, please post what you learn to benefit others in the community.  Thanks!