A Transition Date/Time custom field type represents a |
To add a Transition Date/Time custom field type to your instance:
Issues - > Custom fields.
Add custom field
.Advanced
in the left panel.Transition Date/Time Field
and select it.Next
.Create
Configure
and specify the transitions(s) and the execution of the transition to look for (explained below).If you have upgraded from JMCF |
When creating a Transition Date/Time custom field type, you can configure the Search template as
Using these searchers you will be able to search issues within a date/time range of values for that custom field. The default search template is Date/Time range searcher (Statistics by day). If you select “None” for the searcher, then you won’t see any reference to this field in the Issue Navigator search fields. Note that changing a custom field searcher requires a re-index.
Date/Time range searcher (Statistics by day/week/month/quarter/year) are custom statistics compatible searchers provided by JMCF that allow Date/Time type custom fields of Jira and JMCF to be used in the statistics gadgets. See here for more information.
To specify the transition(s) to look for:
Configure
Edit Transition(s) to look for.
Specify transition names or IDs: You can either manually provide thename
orid
of the transition or use the Transition picker, and optionally specifying the workflow name.
By specifying the workflow name you can use the same calculated field to capture the date/time different transitions with the same meaning across different workflows are executed. For example: Imagine you have two workflows A and B, with transitions 21 and 51 respectively that lead to the Approved status and you want to calculate the date/time of the issue's approval. You can add the two transitions of two different workflows to the configuration as shown below. |
This is the preferred mode, as it allows differentiating between multiple transitions between the same two Statuses, and it also supports "auto-transitions" (that do not change the issue Status). However, it will not work reliably for "old" transitions that took place before major workflow changes or switching the issue to a new workflow entirely. |
Specify from and to Statuses: You can specify the transitions by their From
and To
statuses.
While this option doesn't allow differentiating between multiple transitions that move the issue between the same from and to statuses, and it doesn't work for "auto-transitions" (that do not change the issue Status), it will work reliably even for issues that changed workflows since the transition took place. |
Add
.Save.
To remove a transition to look for:
Configure
Edit Transition(s) to look for.
Remove
for the transition you wish to remove.Save
.To pick a transition using the Transition picker:
Transition picker
in the Configure Transitions
screen.Use Transition Name
- recommended if you want the post-function to search for the transition to trigger by name, which is useful when targeting multiple workflows.Use Transition ID
- if you want to differentiate between transitions that bear the same name.To specify the execution of the selected transition(s) that the field should look for;
Configure.
Latest
or Earliest
from the Transition Execution field to capture the last or first transition execution respectively.By default, the Transition Date/Time field value is displayed using Jira's default date format (if you leave the Date Format
to Default
). However, you can customize it. To select a format for a Transition Date/Time custom field type value;
Configure
Click on Edit Date Format.
Date format
drop-down.Save.
By default, the Transition Date/Time field value is displayed using Jira's default date format (if you leave the Date Column Format
to Default
) in the tabular views. However, you can customize it. To select a format for a Transition Date/Time custom field type value in the List views;
Configure
Click on Edit Date Column Format.
Date format
drop-down.Save.
For example, if you select the COMPLETE
option in the Date Format/Date Column Format
, and the value captured is Thu Jan 25 15:20:34 IST 2018
, then the value will be formatted to 25/Jan/18 3:20 PM
.
You can define a velocity template that will return the Html representation of the calculated custom field on the issue detail view. Leave it empty to use the default template.
To write a velocity template for a Transition Date/time custom field type value;
Configure
Edit Velocity Template
.Save.
You can use the following Velocity variables in the template:
$value
: the raw field value, a Date object$formattedValue
: the field value formatted according to the field configuration aboveFor example:
<div style="border: dashed"> $formattedValue </div> |
You can define a velocity template that will return the Html representation of the calculated custom field on the search list view. Leave it empty to use the default template.
To write a velocity template for a Transition Date/time custom field type value;
Configure
Edit List View Velocity Template
.Save.
You can use the following Velocity variables in the template:
$value
: the raw field value, a Date object$formattedValue
: the field value formatted according to the field configuration aboveFor example:
<div style="border: dashed"> $formattedValue </div> |
The Never show on Transition and Edit screens
option controls whether the Transition Date/Time custom field can appear on transition and edit screens. If you select this option, the field will not be visible on any Edit or Transition screen, even if it is added to the screen.
You can access this field using any of the following getters of the Issue interface
get("Your custom field name") or get("customfield_xxxxx")
that returns a
Timestamp
getAsString("Your custom field name")
or
getAsString("customfield_xxxxx")
that returns a String
representing a date+time