| Name | JIRA Current User Plugin |
|---|---|
| Version | 1.0 |
| Product Versions | 3.6.x-3.10.x |
| Author(s) | Jean-Baptiste Catté |
| Price | Free |
| Download JAR (JIRA 3.6-3.9) | jira-current-user-1.0.jar |
| Download JAR (JIRA 3.10-3.12) | jira-current-user-1.1.jar |
| Download Source | jira-current-user-1.1-src.zip |
Description/Features
Current User is a new user custom field type; it is automatically filled with the current user value.
It was was written in order to solve the JRA-7947 issue. The author problem was to create a new user custom field called Tester and with the Reporter value as default value. This is especially useful for any organization with a Q&A service that is in charge of testing developers work.
This new custom field come with a service: ReporterToCustomFieldService, allowing to copy Reporter value into the new custom field in existing issues.
Installation
Copy the jar into atlassian-jira/WEB-INF/lib/ directory and restart Jira.
Usage
Custom Field
Add a custom field: select Current User as custom field type.
Service
In order to update existing issues:
- Add a new service using class com.sungard.jira.service.ReporterToCustomFieldService.
- Set parameters:
- Target projects list
- The name you gave to your new custom field
This service can be used as a one-shot service, or be ran on a regular basis (if you have not put the custom field as mandatory for example). Only the issues with an undefined custom field value will be updated.
After running the service you have to manually re-index Jira.
In order to get a log file (and know that the service ran successfully) add this section in your atlassian-jira/WEB-INF/classes/log4j.properties file:
log4j.appender.sunlog=org.apache.log4j.DailyRollingFileAppender
log4j.appender.sunlog.File=../logs/sungard-services.log
log4j.appender.sunlog.DatePattern='.'yyyy-MM-dd
log4j.appender.sunlog.layout=org.apache.log4j.PatternLayout
log4j.appender.sunlog.layout.ConversionPattern=%d %p [%c{4}] %m%n
log4j.category.com.sungard = INFO, sunlog
log4j.additivity.com.sungard = false
Version History
- 1.1: Update for JIRA 3.10.
- 1.0: Initial version.
Development
In oder to compile and modify this plugin you'll need Maven 1. Use Maven in order to automatically generate the project files for your favorite IDE.
Source files are UTF-8 encoded.

Comments (13)
Apr 18, 2007
Jason Erickson says:
Thanks for the plugin. It sounds like exactly what I need. Unfortuna...Thanks for the plugin. It sounds like exactly what I need. Unfortunately, for me it seems to work exactly like a User field - I don't see any value defaulted. Does the default only work on issue creation?
I would look at it myself, but ZipGenius is telling me that the zip file with the source code is an invalid zip file.
Apr 19, 2007
Jean-Baptiste Catté says:
I have just tested the sources zip with 7zip, Winzip, and Windows XP compressed ...I have just tested the sources zip with 7-zip, Winzip, and Windows XP compressed folder: it opens fine.
The default value use the standard custom field default value mechanism: it works only on issue creation, after the field value is considered as set (even if it's set to null). But you can set your field as mandatory.
Jul 21, 2007
ardenyang says:
Thanks for the plugin. It's very helpful for me. But I find the plugin can not b...Thanks for the plugin. It's very helpful for me. But I find the plugin can not be use at JIRA 3.10, Because I can not find it at step " Create Custom Field : Choose the field type (Step 1 of 2)".
Could you please take a look?
Thanks again.
Jul 23, 2007
Jean-Baptiste Catté says:
I'm glad it was useful to someone else. ;) Please try this new version: jiracur...I'm glad it was useful to someone else.
Please try this new version: jira-current-user-1.1.jar.
Sep 25, 2007
Gert-Jan Bartelds says:
Hello JeanBaptiste,\\ I just want to report that the 1.1 jar causes JIRA 3.11 to...Hello Jean-Baptiste,
I just want to report that the 1.1 jar causes JIRA 3.11 to hang during startup. The 1.0 version does not cause the same problem. I haven't gone beyond this initial startup tests yet, will report anything else I find. (If I find something)
Cheers, Gert-Jan
Jul 25, 2007
ardenyang says:
Note and Thanks. I confirm The version 1.1 can be used at JIRA 3.10. Thanks for ...Note and Thanks. I confirm The version 1.1 can be used at JIRA 3.10. Thanks for you quick response.
Oct 05, 2007
hernan guelman says:
I have been think for a long time that JIRA is missing a simple feature that let...I have been think for a long time that JIRA is missing a simple feature that lets you see a chart/report showing not only how many issues got resolved last week, but break it by WHO resolved those issues.
can this field be used for that? it will only work if the field gets automatically populated with the current user "resolving" the issue (and not when it is being closed by QA).
Oct 05, 2007
Jean-Baptiste Catté says:
I'm not sure it will work or not, why not try? ;)I'm not sure it will work or not, why not try?
Nov 15, 2007
roro says:
hello everybody, I'm trying this plugin and I just noticed that the current user...hello everybody,
I'm trying this plugin and I just noticed that the current user name value becomes a reporter name value. I saw it when i tried to use in my post function.
Is anybody know how can I do to keep current user name value in my custom field?
Jun 17
Jaan Raamets says:
Hi Great plugin. But is it possible to set the Current User field from incoming ...Hi
Great plugin. But is it possible to set the Current User field from incoming emails too?
Jun 17
Jean-Baptiste Catté says:
I have never tried and I don't know. The plugin uses JIRA API in order to get th...I have never tried and I don't know. The plugin uses JIRA API in order to get the user executing the issue creation.
Best would be to give it a try.
Jun 27
Jaan Raamets says:
It does not work with emails for me :( But now I have second problem too. If I ...It does not work with e-mails for me
But now I have second problem too. If I try to use ReporterToCustomFieldService I get this:
Errors
So I can't define parameters, but the sungard-services.log says:
2008-06-27 14:36:03,037 INFO [sungard.jira.service.ReporterToCustomFieldService] Init Reporter to Custom Field service.
2008-06-27 14:36:03,042 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing target projects keys.
2008-06-27 14:36:03,045 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing custom field name.
2008-06-27 14:36:03,045 INFO [sungard.jira.service.ReporterToCustomFieldService] Init Reporter to Custom Field service.
2008-06-27 14:36:03,048 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing target projects keys.
2008-06-27 14:36:03,052 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing custom field name.
2008-06-27 14:36:03,052 INFO [sungard.jira.service.ReporterToCustomFieldService] Init Reporter to Custom Field service.
2008-06-27 14:36:03,055 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing target projects keys.
2008-06-27 14:36:03,058 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing custom field name.
2008-06-27 14:36:03,059 INFO [sungard.jira.service.ReporterToCustomFieldService] Init Reporter to Custom Field service.
2008-06-27 14:36:03,063 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing target projects keys.
2008-06-27 14:36:03,066 WARN [sungard.jira.service.ReporterToCustomFieldService] Missing custom field name.
2008-06-27 14:36:03,364 ERROR [sungard.jira.service.ReporterToCustomFieldService] Missing or bad projects keys: [], impossible to run Reporter to Custom Fie
ld service.
2008-06-27 14:36:03,381 ERROR [sungard.jira.service.ReporterToCustomFieldService] Missing or bad projects keys: [], impossible to run Reporter to Custom Fie
ld service.
2008-06-27 14:36:03,381 ERROR [sungard.jira.service.ReporterToCustomFieldService] Missing or bad projects keys: [], impossible to run Reporter to Custom Fie
ld service.
2008-06-27 14:36:03,381 ERROR [sungard.jira.service.ReporterToCustomFieldService] Missing or bad projects keys: [], impossible to run Reporter to Custom Fie
ld service.
JIRA Enterprise Edition, Version: 3.12.1, current user plugin 1.1
In regular "create issue" it works fine and our helpdesk staff is happy with that.
Jun 27
Jean-Baptiste Catté says:
It appears that the service is not compatible with JIRA 3.12.x. I'll try to fix ...It appears that the service is not compatible with JIRA 3.12.x. I'll try to fix that.