First/Last Field Change 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 Field Change Date custom field calculates the first or last date that a field was changed. These custom fields help teams track the timeline of field modifications. The First Field Change Date represents the earliest date when a field was changed, while the Last Field Change Date captures the most recent change date. This information can be valuable for tracking the history of critical fields, analyzing trends, or investigating changes made to specific fields.

To create a First/Last Field Change 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 Field Change Date, then click Add custom field.

  5. Fill in the dialog box:

    • Create a name for the custom field.

    • Select the Field(s) that you would like to calculate the first/last field change date on.

    • Specify First or Last – if First is selected, the custom field will calculate the first date that a field was changed. If Last is selected, then the last field change date will be calculated.

  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 Field Change Date custom field can be used for sorting and searching in the issue navigator, allowing you to filter and find issues based on the field change 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 Field Change Date custom field.