Overview
This page provides ready-to-use configuration recipes for common scenarios. Each recipe includes the field type and the settings needed to implement the use case.
Created to Resolved
Goal: Show total elapsed time from issue creation to resolution.
Field type: Time Between Dates
Configuration:
| Setting | Value |
|---|---|
| Start Field | Created (system field) |
| End Field | Resolved (system field) |
| Calendar | Business Hours (or 24x7 for total elapsed time) |
| Display Mode | TIME_SPENT |
| Use Absolute Value | On |
How it works: Calculates working time between the Created and Resolved dates. While the issue is unresolved, the Resolved date is empty: the value is 0 and the state is Inactive until the issue is resolved. To see the time from creation until now on open issues, use Current Date Time as the end field instead.
Countdown to the Due Date
Goal: Show how much working time is left until the due date of an issue.
Field type: Time Between Dates
Configuration:
| Setting | Value |
|---|---|
| Start Field | currentDateTime |
| End Field | Due date (system field) |
| Calendar | Business Hours |
| Display Mode | LEFT_TIME |
| Use Absolute Value | Off |
How it works: The field measures the working time from now until the due date and shrinks as the date approaches. Once the due date has passed, the field stays Active: time left shows 0, and LeftTimeSeconds turns negative by the working time of the overrun. See Countdown / SLA mode.
JQL to find issues with less than one 8-hour working day left:
"Due in.LeftTimeSeconds" >= 0 AND "Due in.LeftTimeSeconds" < 28800 AND "Due in.StateValue" = "Active"
JQL to find issues past their due date:
"Due in.LeftTimeSeconds" < 0
Tips for building your own recipes
- Pick the two dates first: any date or date-time field of the issue works as the start or the end, and Current Date Time turns the field into an age or a countdown.
- Test with one issue: configure the field, run recalculation for a single issue, and verify the result before rolling out to all projects.
- Calendar choice matters: use a business-hours calendar when you want to exclude non-working time. Use 24x7 when total elapsed time matters.
- Combine fields: you can have multiple Time Between Dates fields on the same issue. For example, one from Created to Resolved and another from now to the Due date.

