Hi,
I am using the default workflow of JIRA for my project. On the issue navigator I can display following columns for all the issues in a given project.
Reporter, Created date, Updated date and Resolved date
However, I also want to display Resolved By, Closed BY and Closed Date fields. As there can be multiple Resolved By and Closed By values for an issue, it should show the latest user who either RESOLVED or CLOSED an issue. Same is applied for the Closed date.
I do not see Resolved By, Closed BY and Closed Date columns in the issue navigator's Column Configurations. However, I am sure JIRA must be tracking these values in the database.
The reasong being, I am looking for an on screen view for the project administrator which displays WHO resolved/closed an issue WHEN.
Regards,
Rumit
It tracks those fields in the change history but not as separate fields. If you must need them, you will have to capture those values into custom fields byt setting those values in the workflow post functions.
A useful function to do that is https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Post-Functions#JIRASuiteUtilitiesWorkflowPost-Functions-UpdateIssueCustomFieldPost-Function
You can then configure the issue navigator to include those fields.
This link is not working and I need the same thing, I need to pull the resolve/closed/complete date from history, as well as the date transitioned to inprogress
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joe and Jobin (wow, sounds like bros) :)
Thank you for your help. Your answers certainly helped and I can now track those values and show them on the navigator. Just one more thing I want to ask. Is there anyway I could get these values (Resolved By, Closed By and Closed date) for the issues which are already resolved/closed and show them on the navigator with the same custom fields?
Regards,
Rumit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We capture those during the transition and save them to custom fields using the copy from field post function. We only allows the Assignee to perform transitions so we copy the assignee field. For the date put it AFTER the Update action in the post actions. Otherwise you'll get the last date the issue was updated. Remember to clear them if the issue is reopened or set to unresolved.
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.