I would like to create a custom field, add it to issue types, that shows who updated the issue. I know I can show this on the dashboard, but i would like it as a custom field instead (so can show in lists, etc.). I can't find the code to do this.
I think you can create a single-user picker custom field and an automation rule as below:
{{initiator.accountId}}
Please note that this automation rule will be triggered whenever a Jira issue is updated, and it might use a large amount of the monthly Automation usage.
https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update
Thank you.
Ah! k, I think I may not go that route, but use issue security instead. My end goal was to either know who had changed something, or prevent them from doing so in the first place. Issue security seems to be the better option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Jo-Lee Bertrand
Adding a custom field is one step. Updating the custom field each time the issue is updated is another step. With which step do you need help?
Do you want one field that shows the person and the date, or two fields?
What is the type of the project with which you are working? Get that information from the Type column on the View All Projects page under the Projects menu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello!
Adding the custom field I think I am good with. I am assuming it needs to be either a text field or JIRA user field.
Company-managed software project. I have gotten to the step of creating a rule that updates a field, but I don't know the smart value for the person who last updated the issue.
Any help is much appreciated!
J
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jo-Lee,
Please show us screen images of the rule that you have built so far.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
I decided to go in a different direction. Largely I was worried about folk editing issues after they had been marked approved etc. (and I wanted to capture who last updated because of that) so what I did was install issue security. I think I won't be going down the route of the rule any longer but thank you for reaching out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.