Setting a reporter based on a different project lead

[Stanisław Juźwicki]

Hi,

I have a bit of a struggle with this requirement:

When someone creates an issue in project A, there should be a (linked) issue created in project B. The reporter of the newly created issue should be the project lead of the project where the trigger issue was created (so the lead of project A in this case).

The main part of the automation works without any problems, but setting the reporter based on the trigger issue project lead does not work. I am trying to set up the reporter in the additional fields of the action that creates the issue. This is the syntax I have tried:

"reporter": "{{triggerissue.project.lead.accountId}}"

"reporter": "{{triggerissue.project.lead.name}}"

I see that the rule tries to do something, because the reporter of the newly created issue is set to "Anonymous" after the issue is run (normally it was "Automation for Jira". An important piece of information might be that we are using single sign-on with Azure AD, so this might complicate things, but still I would assume that either name or accountId should work.

[Victor Seger · Accepted solution]

Hi Stanislaw,

I'm Victor from Automation for JIRA Support Team.

I've made some testing here and it seems that your smart values are very close from the one I've tried and which worked fine:

{{triggerissue.project.lead}}

Can you please give it a try with this smart value and let me know how it goes for you?

Cheers,

Victor - Automation for JIRA

[Stanisław Juźwicki]

Hi Victor,

Unfortunately I still get Anonymous reporter when the rule is run. The audit log shows a full success (because the rule does in fact create a new issue), so I have no way of debugging it (and I cannot trigger it manually).

I am attaching my full rule definition (although there is nothing really complicated there I guess) and the result on the newly created task.

On a side note, I had a similar result (a task was being created but the reporter was Anonymous and there was no option to change it) when the user creating the task had no global permission to "Browse users". Could it be an issue that the "Automation for JIRA" virtual user does not have this permission? As far as I know I cannot set permissions explicitly on that user...

[Victor Seger]

Hi Stanisław,

Thanks for your quick reply.

Sorry for not being that specific previously.

I've used the following configuration under the "Reporter" field on your "Create Issue" action:

I've tested also with the Additional fields and it really didn't seem to work.

So, my suggestion is for you to remove the "Additional fields" configuration and set the Reporter field only by selecting the field under "Choose fields to set..." and then adding the smart value sent previously.

Can you please give it a try again and let me know how it goes?

Cheers,

Victor

[Stanisław Juźwicki]

It did work now, thanks a lot!

I will now need to test it with actual production examples, because I have rules that do need to use additional fields, but not for setting reporter values.