Thanks for taking the time to raise this issue.

Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com

Thanks, Adam. I tested it. It worked fine in my jira 4.3. thanks your tip....^_*

I tried the "JIRA Current User Plugin" described above still worked for me with Jira 4.3 in a test system. Just use the latest available version (jira-current-user-1.2.jar)

Hello, every one.
So.... Does it has any way to make this function in jira 4.X?

thanks.

Would be nice. This plugin (https://plugins.atlassian.com/plugin/details/5155) would solve it but does not seem to be compatible with out version.

It would be great if the user picker could begin with a user group such as testers, or participants, and then underneath have a complete list of users.

HI ALL!!

We have JIRA version 3.12 and we installed this plugin JIRA Current User Plugin. So far no trouble using it and people id delighted. But now we are trying to see it in English and there´s no way.

We installed Jira having spanish as default language. And even if other plugin adjust themselves when a person changes its default language at their profile, this one does not .

Can anyone help me??

I just revisited this issue and that plugin appears to be what I need. I ended up writing sqlstatements to change the existing User Picker field to the new type, and then to change all the special 'reporter' values to the actual user that reported the issue. I will include them here in case there is someone else out there in the same situation as me that would benefit from it.

Keep in mind this was already a user picker and was a required field so all the data in there was already appropriate for the new field type.

First sql statement changed the custom field type:
update customfield set CUSTOMFIELDTYPEKEY='com.sungard.jira.plugin.currentuser:currentuser', CUSTOMFIELDSEARCHERKEY='com.sungard.jira.plugin.currentuser:currentuserpickergroupsearcher' where cfname='Tester'

Second sql statement changed the special 'reporter' user we were using to the actual reporter:
update customfieldvalue As cfv, jiraissue As ji SET cfv.stringvalue=ji.reporter WHERE cfv.issue = ji.id AND cfv.customfield=(select id from customfield where cfname='Tester') AND cfv.stringvalue='reporter'

It is best to do this while jira is shutdown, and I believe a re-index is mandatory once it is brought back up.

I used http://confluence.atlassian.com/display/JIRA/Database+Schema and http://confluence.atlassian.com/display/JIRA/Changing+Custom+Field+Types as references.

Thanks for writing this plugin, it is incredibly useful.

I still think this would be a reasonable feature to have in the base product, but that is just one guy's opinion.

Hi,

I'm not sure of what you want to do exactly, but perhaps you just need the Current User Plugin, which is a user custom field with current user as default value.

I solved this problem by creating a new plugin: JIRA Current User Plugin. The default value of this new custom field is not "Reporter" but the current user. There is also a service allowing to copy reporter value into this field for old issues.