Available as of 6.6. The field answers one question: how much working time passed between the moment the issue first reached one group of statuses and the moment it first reached another? Lead time (“from Open to Done”), time to first reaction (“from New to In Progress”), time to resolution - each is one field with two lists of statuses.
What it calculates
The value is the working time by the selected calendar from the first entry of the issue into any of the start statuses (A) to the first entry into any of the end statuses (B). It is a number in the unit you pick for the field: with the unit hours, 7200 seconds of working time is shown as 2.0.
The value is calculated on the fly from the issue history. It is a finished interval, not a running counter: until the issue reaches B the field is empty, it does not tick. To search issues that have not reached B yet by the time passed so far, use realTime().
Set up the field
- Administration → Issues → Custom fields → Add custom field, and choose Time between statuses. In the list of Jira field types it carries the app’s prefix, like the Transition counter.
- Add it to the screens of the projects that need it.
- Open the field’s context and configure it:
| Setting | What it is |
|---|---|
| Start statuses (A) | One or more statuses. The interval opens on the first entry into any of them. |
| End statuses (B) | One or more statuses. The interval closes on the first entry into any of them. |
| Work calendar | Only working time by this calendar is counted. |
| Unit | The unit the number is shown, searched and exported in - for example seconds, minutes, hours, days. |
Calculation rules, with examples
Start statuses A = Open, end statuses B = Done, unit hours, a calendar of 09:00-18:00 on weekdays.
| History of the issue | Value | Rule |
|---|---|---|
| Created in New; Open on Monday 10:00; Done on Monday 12:00 | 2.0 |
Working time from the first entry into A to the first entry into B. |
| Open on Monday 10:00, still In Progress | empty | B is not reached yet - the field is empty, there is no running value. |
| Never in Open; Done on Monday 12:00 | empty | A never happened, even though B did. |
| Done on Monday 10:00, then Open on Monday 11:00, then Done again | 0 |
The end is not later than the start - the value is 0. |
| Open 10:00, Done 12:00, reopened to Open on Tuesday, Done on Wednesday | 2.0 |
Only the first entries count: re-entering A after B does not change the value. |
| Created directly in Open on Monday 09:00, Done on Monday 18:00 | 9.0 |
An issue created in a status of A starts the interval at the creation date. |
JQL and export
The field is searched as a number - exact value and ranges:
"Lead time" > 5
"Lead time" >= 1 AND "Lead time" < 8
cf[10500] > 0
The number is in the unit of the field: with the unit hours, "Lead time" > 5 finds the issues that took more than five working hours. An empty value (B not reached, or A never entered) matches "Lead time" is EMPTY.
Live search: realTime() and realTimeBetween()
As of the release after 6.6.0 (Jira 10 and Jira 11.3) the field also takes the live search functions realTime() and realTimeBetween():
cf[10500] in realTime(">", "2h")
"Lead time" in realTimeBetween("1h", "4h")
cf[10500] in realTime(">", "2h") finds the issues whose working time by the calendar of the field, counted from the first entry into a start status (A), is more than 2 hours:
| Issue | Time compared with the condition |
|---|---|
| Has reached an end status (B) | The final value of the field. |
| Has entered A, has not reached B yet | The working time from the first entry into A up to the moment of the search. |
realTimeBetween("time", "time") works the same way with a range: the time is between the two bounds. The time strings are the same as for the other fields - see Functions take the following parameters.
So with realTime() you can find issues that are still on their way to B and already over the threshold, which a plain number search cannot do: until B is reached, the value of the field is empty.
Switch the search template and re-index
The live functions need the search template Time between statuses searcher (realtime):
- Administration → Issues → Custom fields, find the field, and choose Edit details.
- In Search template, choose Time between statuses searcher (realtime) and save.
- Run a re-index.
Do this for each Time between statuses field you want to search live, after you update the app.
cf[N] > …, is EMPTY and sorting - but realTime() and realTimeBetween() fail with a JQL error that names the search template Time between statuses searcher (realtime).
Export
CSV and Excel export carry the value as a number in the same unit, so it can be summed and averaged in a spreadsheet without parsing.
Cloud
The field has no counterpart in Cloud and is not transferred by JCMA. The export warns about every Time between statuses field it skips. See What JCMA transfers to Cloud.
The field settings are also available through the REST API for Jira administrators: Time between statuses - field settings.

