Page Comparison

...

This field represents the number of Affected Versions.
<!-- @@Formula: issue.get("versions").size() --> 

The formula itself is a Java-style expression that can reference any issue field value, include arithmetic operators as well as any other Java operator, and Java method calls (such as the .size() example above). Access to issue field values is achieved by the following syntax:

...

1. Create a new custom field, choosing "Transition Date/Time Field" for its type.
2. During step 2, in the Description field, include the transition ID(s) (recommended) or name as described below.
3. Optionally, specify whether you want the first or last execution of the transition(s) ^{(new in 1.2.5 and 1.5.2)}
4. Re-index your data, as JIRA will kindly suggest you to.

Indicating the transition

The transition(s) should be indicated in the field description inside an html comment (so that it remains invisible when showing the field description), preceded by the following keyword: @TransitionId: or @TransitionName: (note the colon at the end). For example:

 <!-- @TransitionId: transition ID --> 

or

 <!-- @TransitionName: transition name -->

If you use @TransitionId, you can specify a list of transition IDs, separated by commas ^{(new in 1.2.5 and 1.5.2)}:

<!-- @TransitionId: transition_ID_1 , transition_ID_2 -->

You can naturally include the real description of the custom field as well. For example:

This field represents the date and time of the Resolution of this issue.
<!-- @TransitionId: 5 -->
<!-- @Execution: last -->

Specifying whether to capture the first or last transition execution

You can also specify whether to capture the first or last transition execution, using the @Execution: keyword followed by first or last. For example:

<!-- @Execution: first -->

If you don't specify anything, the last execution will be captured.

...

1. Create a new custom field, choosing "Transition Caller Field" for its type.
2. During step 2, in the Description field, include the transition ID (recommended) or name as described below.
3. Optionally, specify whether you want the first or last execution of the transition(s) ^{(new in 1.2.5 and 1.5.2)}
4. Re-index your data, as JIRA will kindly suggest you to.

Indicating the transition

The transition(s) should be indicated in the field description inside an html comment (so that it remains invisible when showing the field description), preceded by the following keyword: @TransitionId: or @TransitionName: (note the colon at the end). For example:

 <!-- @TransitionId: transition_ ID --> 

or

 <!-- @TransitionName: transition_ name -->

If you use @TransitionId, you can specify a list of transition IDs, separated by commas ^{(new in 1.2.5 and 1.5.2)}:

<!-- @TransitionId: transition_ID_1 , transition_ID_2 -->

You can naturally include the real description of the custom field as well. For example:

This field represents the Resolver of this issue.
<!-- @TransitionId: 5 -->
<!-- @Execution: last -->

Specifying whether to capture the first or last transition execution

You can also specify whether to capture the first or last transition execution, using the @Execution: keyword followed by first or last. For example:

<!-- @Execution: first -->

If you don't specify anything, the last execution will be captured.

...