Skip to main content

Field Change Count

A Field Change Count field counts how many times a field you choose changed on a work item, such as the due date.

To count status moves with from and to statuses, use Transition Count instead.

What you see​

On the work item and in lists, you see a whole number, such as 3.

A field that never changed shows 0.

When you hover over the value, you see when it was last updated.

Search, sorting and CSV exports use the same number.

Settings​

SettingWhat it doesDefault
FieldThe field whose changes count. You must pick oneNone
Don't count changes from an empty value (setting a value for the first time isn't counted)Skips changes where the field had no value beforeOff
DisplayA plain number, a traffic light or a progress barPlain number

One save that changes the field counts once.

Field lists only fields that Jira keeps a change history for. Fields such as Created, Updated, Comment and Watchers, and other FieldCraft fields, don't appear.

Example: count due date changes​

You want to see how often the due date moved after someone first set it.

  1. Create the field from the Due date changes recipe, or open the configuration page of a Field Change Count field.

  2. In Field, select Due date (duedate).

  3. Select Don't count changes from an empty value (setting a value for the first time isn't counted).

  4. Select Save.

Result: A story whose due date you set once and then moved twice shows 2.

Search with JQL​

JQL compares the stored number.

To find work items whose due date moved more than once, most changes first, use:

"Due date changes" > 1 ORDER BY "Due date changes" DESC

You can also use the field ID, for example cf[10149] > 1.

When the value updates​

FieldCraft recalculates the field when the work item changes.

Existing work items get a value when someone opens them, or when you recalculate existing work items.

See How values stay current.

Things to know​

  • Clearing a field counts as a change. With the checkbox on, setting it again afterwards doesn't count.

  • Until you save the configuration for the first time, the field stays empty.

  • In Jira's list of field types, this type is FieldCraft: Field Change Count.