Reporter set to empty ONLY when cloning ticket

[Jeffrey Bistrong]

I have been running into an issue recently where the reporter is being set to empty ONLY when cloning tickets. 

This is happening in both the production and sandbox instance of jira. I raised this ticket with atlassian and so far they can't figure out what is causing the problem, so I figured I would post here to see if anyone else is running into this issue?

[Jeffrey Bistrong]

As a work around I put automation in place to set the value of the reporter from the issue.creator value. 

[John Funk]

Hi Jeffrey,

That's strange. However, it says Anonymous for the Assignee, which is different from "Unassigned". How is the Reporter being populated in the original work item? What type of user is this - Jira licensed user, Customer, etc.?

[Jeffrey Bistrong]

fully licensed jira user with the appropriate create permissions on a project. once the ticket is cloned I am able to go to the ticket/reporter field and set it to the proper person. 

[John Funk]

How are you doing the clone? Manually? Through automation? 

[Jeffrey Bistrong]

manually, via the clone button from the hamburger menu drop down. and in sandbox no automation exists since it doesn't get copied down as part of the sandbox copy process

[Jeffrey Bistrong]

[John Funk]

Don't know what to tell you. Is it just this one ticket that does it? Or multiple tickets? Have you tried to change the Assignee before the clone - like to you? 

[Jeffrey Bistrong]

happens with every ticket that is cloned across our sandbox and production instances by every user

[John Funk]

Last desperate stab - who is the actor of the rule when if fires? 

[Bill Sheboy]

Hi @Jeffrey Bistrong and @John Funk 

There is a new defect just created for this symptom: https://jira.atlassian.com/browse/JRACLOUD-94687

Did your team create that one, Jeffrey?

Kind regards,
Bill

[John Funk]

Weird stuff! That being case, try adding a manual rule that instead of cloning the issue will create an issue and then you will need to list all of the fields you want "cloned" and copy in the trigger issue value. This would include the Assignee field. Hoping there are not a lot of fields on the screen that need to be copied. 

[Jeffrey Bistrong]

Atlassian confirmed this is a bug: https://jira.atlassian.com/browse/JRACLOUD-94687

[Jeffrey Bistrong]

@Bill Sheboy yes, I they just confirmed that bug, which was created out of my support ticket. It is odd nobody else reported this behavior

[Bill Sheboy]

Yes and...I recall several community posts for the last three weeks (or so) where the Assignee was set to the Reporter mistakenly, and other weird behaviors around Reporter.  I wonder how these symptoms may be related.