First/Last Resolution Date Custom Field

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

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

The JEP Resolution Date custom field holds the date when an issue's resolution field changes from EMPTY to any value. These custom fields help teams track the resolution timeline of their issues. The First Resolution Date provides insights into when an issue was initially resolved, while the Last Resolution Date captures the most recent resolution date. This information can be useful for monitoring issue resolution times, identifying trends, and evaluating the team's performance in resolving issues.

To create a First/Last Resolution Date 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 Date tab on the left-hand side of the dialogue. 

  4. Select Resolution Date, 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 of selected status(es). 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 Resolution Date Custom Field can be used for sorting and searching in the issue navigator, allowing you to filter and find issues based on the resolution date.

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 Resolution Date Custom Field.