First/Last Resolved User Custom Field

Owned by Tuncay Senturk
Last updated: Sept 04, 2023 by Derya Özdemir
3 min read

This page is about JEP Cloud. Using Jira On-Prem? Click the On-Prem button above.

The First/Last Resolved User custom field helps track the user responsible for changing an issue's resolution field (which represents the final state or outcome of an issue in Jira) from EMPTY to any value. By utilizing this custom field, you can gain insights into the user who initially resolved the issue and the most recent user who made changes to the resolution field. This information allows for better tracking and analysis of the resolution history of issues, providing transparency and accountability for the resolution process.

To create a First/Last Resolved User Custom Field, follow these steps:

  1. Navigate to Apps > Enhancer Plugin for Jira > Custom Field Configuration.

  2. Click the Add New JEP Custom Field button.

  3. Click the User/Group tab on the left-hand side of the dialogue. 

  4. Select Resolved User, then click Add custom field.

  5. Fill in the dialog box:

    • Create a name for the custom field.

    • Specify First or Last as the issue can be resolved multiple times. If first is selected, the calculation will be done according to the first occurrence. Otherwise, the last one will be calculated.

    • Enable the Clear when re-opened box if you want the field to be cleared when the issue is reopened.

  6. Click the Save Custom Field button to create the custom field. The custom field will now appear in the issue view:

Once created, the First/Last Resolved User Custom Field can be used for sorting and searching in the issue navigator, allowing you to filter and find issues based on the user who initiated their status transitions.

Remember to add this custom field to the appropriate screens so that it can be visible and accessible when working with issues. If you don’t know how, check out the Jira documentation.

It's important to note that for new or updated issues after creating this custom field, the custom field values will automatically update correctly. However, for existing issues, it's necessary to regenerate the issue in order to see the correct values associated with the First/Last Resolved User Custom Field.