When viewing an issue, I want to display not noly who the issue is assigned to, and who the reporter is, but also who created the issue. We have some circumstances where issues get pinballed around (including the reporter), that it would be helpful to know who originally created the issue.
Ah, yes, I create a user picker field called "creator" and populate it during the "create" transition. Never put it on an edit screen, job done.
I think I use a post-function from the Jira Suite Utilities to set the user to %current user%
Maciej, when you try to use the "Copy Value From Field to Field" post function, "Current User" is NOT an option in the Source drop-down list. Of course, it should be an easy thing to do, but unfortunately, they left out this very basic functionality.
The easiest way I found around this problem was to use the "Set field value from User Property value" post function. Unfortunately, I could not find the right key word to use for the "Source User Property name (key):" field to refer to the built-in user's name. So, I had to create a user property called "name" in the User Management area and manually populate that with the user's name. Then, I used that as the source in my post function. Of course, for the custom field that I created for the destination, I had to create it as a text field, as opposed to a user picker. When I tried it as a user picker type, the value was still blank after it tried to set it to the user's name property.
I realize that is a rather kludgy work-around, but in all honesty, we shouldn't have to try and jump through hoops simply to set a custom field's value to the Current User. Unfortunately, it appears that due to the current limitations in this system, we have no choice but to find our own workarounds for this basic piece of functionality. I mean, the Current User is easily known to the software at that point, and in fact, you can Assign to Current User (which just updates the Assignee field). So, we should be able to choose "User Name" as the source to set a custom field's value.
Maciej, I am using the OnDemand suite, so if you are using the installed version, I suppose there may be different choices for the Post functions.
Nic, if you could share which post function you used, I would greatly appreciate your help, as I couldn't replicate your suggestion. When I tried to open the "Copy Value From Field To Field" post function, the source field was limited to the drop-down list of existing fields (current user was not an option). When I tried the "Set Field Value From User's Property Value" post function, I tried putting "%current user%" in the Source User Property Name (Key) field, but it did not populate my custom field. All of the other post functions I saw related only to the "simple issue fields", and thus could not be used for my custom field. I'd love to know how you accomplished this exactly, as I have the same question that I'm trying to work through right now.
I just now realized that you probably have the installed version, and I am trying this on the OnDemand suite. However, due to Crucible/Fisheye not working with GitHub hosted projects in the OnDemand suite, we are now planning on going the installed route, so if you could share with me how you did this in the installed version, it would save me a little time during my setup.
I am trying to do something similar. When an issue is resolved I would like a post function to record the current user into a custom field called "Resolver". We are using this to support certain reporting needs. We run the installed version.
Did you ever figure out the script to use? Thank you for any help,
Hi all! Lauren here from the Enterprise Cloud marketing team. I have some exciting Cloud updates from #AtlassianSummit that I wanted to share. We want everyone in your organization to be ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs