Automations to Create issue types across different projects

[Jeff Lombard]

I have created a automation that triggers when I change the status of a issue in Jira Service Management Project. It will create a new issue in our standard Jira Project. 

I want the Assignee in the Service Management Project to be the Reporter in the Jira Project, so I used the following JQL to Set the Reporter

• {{issue.assignee.displayName}}

I am getting an error that says the user is inactive. In my test I am the Assignee and I am a admin in both projects. I am not sure why this is happening. 

• I have checked my account in both projects and it is active. 
• I do not have inactive accounts in either project. 
• I have necessary permissions in both projects to be assigned as a reporter

[Mark Segall · Accepted solution]

Hi @Jeff Lombard - Who is the automation rule actor?  That's the account that will require permissions for setting the reporter on the target project. If it is Jira Automation, you will need to ensure that the Project Role (atlassian-addons-project-access) is accounted for in the permission scheme of the target project.

[Jeff Lombard]

Yes, atlassian-addons-project-access.  Is listed in the permission scheme of both projects. 

Below are some screenshots of the fields I am setting and the error message I get. When I remove the "Reporter" mapping from the rule everything works fine and creates the new issue as expected. The "Reporter" on the new ticket shows as "Automation for Jira" when successful. 

 

[Mark Segall]

Thank you for the screenshot.  This adds much more context.  The issue is that you're trying to populate with the display name.  You only need {{issue.assignee}}

Additionally, you don't even need the smart value. From the ⋯ menu on the right, you can simply select copy and then select what field you're copying from.

[Jeff Lombard]

That did the trick! Thank you for catching that.