You don't. The creator is a special field that was introduced a while back because it can be important to know which user entered the issue. The problem came about because JIRA has a "reporter", but people are able to change that - it's especially useful when you're entering issues on behalf of someone else. The creator is intended to capture, literally what it says, the person who physically created the issue. It should not be changed, and there's no good reason to want to change it.
Also, it's mostly a field that you don't usually use a lot. If you want to look at who asked for something (but may not be the person who created the issue), use Reporter.
Could you please explain why you want to do this so we can guide you on using it properly?
I have a similar situation where I would like to change the issue creator. In my situation I want a logged in user to be able to submit an improvement suggestion anonymously. I can set the reporter to anonymous, but I cannot change the creator field, which continues to show up in the issue history tab (i.e. "username created issue - just now"). Is it possible to do in script runner or another plugin? If not could I at least suppress the user name from the change history view on the history tab? I have anonymous issue creation enabled, so they could log out and create the issue, but I would like to make it as easy as possible for them and not require them to log out.
My situation is, that our user creates an Accident Report for HR. Thats fine.
This issue will clones and link (groovy) to the security department without fields like name and reporter for privacy reasons. I can null the reporter but the creator is the user wo creates the initial accident report. I don't won't to have these information in the cloned task.
Here is a situation..
Creator has left the company and dont want to see that name(identity) listed as creator on the tickets. Its approporiate to shift responsibility to another staff member re "creator".. This is part of removing vestiges of former staff member from process.
To get around this, am deleting tickets and starting brand new ones with same information.. not very pretty.
For the record: I totally agree, with your advice to not mess with the creator.
However, there is one requirement, I'm running into in 2021:
For GDPR compliance, legal demands that any reference to individual persons is to be purged 12 months after an issues close.
And since ianal, we ususally have a hard time, challenging demands from legal....
If you use the Jira Importers Plugin (JIM) to import issues, the user logged in (the one who uses the plugin to import) will be set as the "creator" of every single issue. It seems one can't do anything about that. I think that would be really a case where the ability to change the "creator" could be useful.
My problem is that we create some tickets for our users and if we change the reporter field to that user they still don't see the ticket in their queue as they are not the creator.
It would be ideal for users to be able to view the tickets that have them assigned as reporter, or be able to alter the creator.
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events