Overview
Time Between Dates fields use schema properties for JQL searching.
The general syntax is:
"Your Field Name.PropertyAlias" operator value
Where Your Field Name is the name of your Time between dates custom field in Jira.
The property alias goes inside the same quotes as the field name, after a dot: "Resolution Time.SecondsValue" > 3600. Square brackets around the alias, a dot after the closing quote, and a custom field ID (cf[N], customfield_N) instead of the name do not work: Jira search answers such a query with an empty result instead of an error. JQL also cannot compare one field with another - the right side of a comparison is always a value.
Searchable properties
| Property | Type | Description |
|---|---|---|
| DisplayValue | text | Formatted time string |
| HoursValue | number | Hours component |
| MinutesValue | number | Minutes component |
| SecondsValue | number | Total elapsed time in seconds |
| TimeInHoursValue | number | Total elapsed time as decimal hours |
| TimeInMinutesValue | number | Total elapsed time in minutes |
| StateValue | text | Current state: Active or Inactive |
| GoalTimeSeconds | number | Goal in seconds: the working time between the start and end dates |
| LeftTimeSeconds | number | Remaining time in seconds. In countdown mode (currentDateTime as the start field) it turns negative once the target date has passed |
| DateNextUpdate | date | Next scheduled recalculation |
Query examples
Find issues where time between dates exceeds 5 days
"Resolution Time.TimeInHoursValue" > 120
Find issues resolved within 4 hours
"Resolution Time.TimeInHoursValue" <= 4
Find active (still calculating) fields
"Resolution Time.StateValue" = "Active"
Sort by resolution time
project = "MY-PROJECT" ORDER BY "Resolution Time.TimeInHoursValue" DESC
Notes
- Replace
"Resolution Time"with your actual field name. - If the field uses
currentDateTimeas the end date, values update periodically. - Text property searches are case-sensitive.

