Global Automation Rule Issue- Copying Reporter to Linked Issue

[Harry Rumble]

We have a Global Automation Rule that runs as follows:

When: Issue Linked

If: Issue matches JQL

created > -1m

And: Some linked issues match:

Types= All linked typesMatch: project = "ITSD" (our service desk)

Then: Edit issue fields

this action is set "Choose to Set fields" and the additional field script is:

{
"fields": {
"reporter": {"name":"{{destinationIssue.reporter}}"}
}
}

The issue is the rule only runs successfully when the "source issue" (issue that linked issue is being created from) has the relationship types "causes, duplicates, precedes, etc"

In other words, if the linked issue has the link type "is caused by", the reporter does not copy over, but if the link type is "causes" the reporter is copied successfully. 

I have changed the rule multiple times but cannot get the reporter to copy over no matter what the link type is, which is what we are looking for. 

Am I missing something that will allow a reporter of a issue to be copied over to the linked issue?

[John Funk]

Hey Harry,

Have you thought about trying with the rule ONLY using "is caused by" link to see if it works. Might be easier to troubleshoot from there if it doesn't. And of course, be sure there is an existing link of that type between the issues.   :-)

[Harry Rumble]

John,

The weird thing is, this rule is to set to run in all issue links, but will only run in the specific scenario listed above. It should be running no matter what the issue link is.

-Harry

[John Funk]

I understand - but thinking there is something not right with the data for that type in that instance. 

[Harry Rumble]

Yes, John, when I changed the rule to use only "is caused by" it does not work at all. Where would I resolve the data for this instance?

[John Funk]

Figured that might be the case. I don't know if there is permissions thing going on or not. One step in that direction might be to change the link type to another one that works and see if it is really the link type or the actual issue that is linked to it. 

[Harry Rumble]

John, permissions are all set, as the users who would be creating the linked issues have permission to modify reporter in all projects. 

[John Funk]

Did you run through the test above?

[Harry Rumble]

Yes, I tried just using both relationships for the rule. Same behavior

[John Funk]

No no matter which link you use for that one issue, it always fails?

[Harry Rumble]

It's strange, if the "is cause by" link is used, it works fine. The "causes" link does not work, it either will not change the reporter on the created linked issue, or when I adjusted the rule slightly, it changes the reporter of the source (trigger) issue to the reporter of the newly created linked issue, which is the Service Desk agent. So on the source issue, the reporter/assignee are the same.

I cannot even create a new rule that performs this action, so I wasn't sure if there was a certain setup that was needed, or if our Issue Linking has the problem

[John Funk]

I would open a support ticket with Atlassian to get to the bottom of it. One offs like that can take days to troubleshoot.  

https://support.atlassian.com/contact/#/

[Harry Rumble]

Thank you John!