| Excerpt | ||
|---|---|---|
| ||
Calculates the issue's last transitioned date. |
The Last Transitioned Date Custom Field does exactly what it says on the tin - it calculates the issue's last transitioned date.
To Create a Last Transitioned Date Custom Field
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This page is about JEP for Jira DC. Using Cloud? Click here. |
The First/Last Transitioned Date custom calculates the date when an issue underwent a transition.
On this page:
|
|---|
Step 1: Create a First/Last Transitioned Date custom field
From Jira settings, navigate to Manage Apps.
From the side menu, find
Enhancer Plugin for JIRA.Click Custom Field Configuration.
Click the Add new JEP custom field button.
Click the Date tab on the left-hand side of the dialogue.
Select Transitioned Date, then click Add custom field.
Step 2: Configure the field
...
Fill in the dialog box:
...
- Pick JEP - Last Transitioned Date in the custom field drop-down menu.
- Create a Name for the custom field.
...
Name – Create a name for the custom field (this will appear on screens and can be used in JQL)
Skip self transitions – If you enable this, the transitions made by the user themselves won’t affect this field.
Click the Save custom field button.
| Tip |
|---|
You must link the custom field with the appropriate screens to see them. For more information, refer to the Jira documentation. |
Usage in JQL searches
You can use the Transitioned Date custom field in your JQL searches to filter and sort issues based on their resolution time.
| Excerpt | ||
|---|---|---|
| ||
Calculates the issue's first or last transitioned date. |