change Creator of issue to another user

[Maciej Łukasz Wojszkun]

Hi, I search community for my case, but I don't found answers. But I believe in multi-brain community :)

My case: someone from company wants to create issue with a suggestion to executive management. And he/she wants to be anonymous.

So, I want to anonymize issue in one project that any information of creator/reporter is set. 

Change reporter - of course its trival, but... what with creator? Can I write a script which set Issue Creator as eg. jirabot user? 

The second way is create issue from email... but still we can found a email and see who sent it.

Any tips can be useful!

[Maciej Łukasz Wojszkun · Accepted solution]

I found nice resolution:

def authContext = ComponentAccessor.getJiraAuthenticationContext()
if (CFvalue == createAnonymously) {
  def jirasparrow = ComponentAccessor.getUserManager().getUserByName("jira_sparrow")
  authContext.setLoggedInUser(jirasparrow)
  issue.setReporter(jirasparrow)
}

and place it as Post Function on create transition (before issue creation) 

[Rit]

Hey @Maciej Łukasz Wojszkun , 

Could you please explain a bit on this solution or if there was any better solution in the recent days ? 

edit: ComponentAccessor.getJiraAuthenticationContext().setLoggedInUser(unknown-user) is not changing the creator. But I see the change in the reporter. 

EDIT 2: It's working perfectly. My bad I was trying it in Groovy (JMWE) plug-in in the Post condition after doing it in th escriptrunner plug-in it works perfect. Thanks a lot :v:

[Nic Brough -Adaptavist- · Accepted solution]

Reporter isn't a problem, you can set someone else as the reporter of an issue when you create it.

Creator is more of a problem for you.  It gets captured when you create an issue, and then cannot be changed.  Even if you could change it (you don't really want to though), a change would be recorded in the history.  It's a different thing to reporter, and was added to help Jira act like a service desk (before JSM had been acquired and rebuilt by Atlassian!).  The thought was "customer rings Agent, Agent enters issue, sets the reporter to  the customer, and Jira keeps the Agent as the creator being the person who created the issue, rather than the person needing the help.

As you suspect, you need to capture an empty or dummy creator in these cases, at the time of creation, not change it later.

Michael has given you docs on one way to do it, but you could also let your project (do not do this if your server is exposed to the internet, it must be inside your organisation's networks, so only people of your organisation can get to it.  You can then make "create issue" possible for people who have not logged in yet.  Creator" will be empty or anonymous.

A third option might be to write a Scriptrunner script that can blank out the creator if they are on a list of people who should not be reported.   That assumes you have Scriptrunner for Server installed of course.  (It can not do it on Cloud)

[Maciej Łukasz Wojszkun]

Hi @Nic Brough -Adaptavist- 

thanks for reply.

Yes, Scriptrunner will be the best solution, but in there's no setCreator method in API. Do you have any tip?

Now I have an idea to re-create issue using Scriptrunner (user creates issue, postfunction create a second issue, and delete the first one). I have to check if creator of the second issue will be different than as is in the 1st issue.

[Nic Brough -Adaptavist-]

Yes, it's not as simple as making a setCreator call on a mutableissue, you have to go down to a lower level.

Copying the issue would work, but it's very clumsy and a lot of work.

In both cases though, I very much doubt it is worth the effort.  It would be far easier to create an issue collector on a page for reporting anonymous suggestions,  or set the project up as a helpdesk that can take anonymous reports.

[Maciej Łukasz Wojszkun]

Thanks, 

but the plan is create standard issue, with option (in custom field) for anonymize creator. 

What do you mean talking "lower level"? database?

[Nic Brough -Adaptavist-]

An issue collector can do that.

For doing it in a script, lower level means that your code would need to reference calls in Jira's API that get to the data via the field, rather than the issue, and some of that is not documented.

You could also do it in the database, but there's a problem with that - you need to stop Jira, get a proven backup, use SQL to empty the field (or better, put in the id of a dummy placeholder user), restart Jira, and re-index it.  For this change, if you used a placeholder user, the re-indexing would only need to be done for the project.

[Michael Yaroshefsky - Visor for Jira]

Hi @Maciej Łukasz Wojszkun ,

Did you get a chance to read this support article, "How to allow users to create issues anonymously?"

If not, here's the link https://confluence.atlassian.com/jirakb/how-to-allow-users-to-create-issues-anonymously-192551.html

The article suggests that you can use the issue collector, which provides an anonymous way for users to create issues. 

Please let us know if this helps,

Michael

[Maciej Łukasz Wojszkun]

Hi @Michael Yaroshefsky - Visor for Jira 

as I see, your option need to place some www page outside of jira. This is not the way I want. :)