- What is a goal?
- Goal types
- Default goal
- Conditional goals (JQL-based)
- Goals are always re-evaluated
- Tips
What is a goal?
A goal is the target time for a Timer field. When elapsed time exceeds the goal, the timer is marked as Failed. Goals let you define SLA deadlines - for example, “respond within 4 hours”, “resolve by end of the next business day”, or “deliver by the date in the Due Date field.”
Goal types
A goal does not have to be a fixed duration. Three kinds are available:
| Type | What it means |
|---|---|
| Time String | A fixed budget written as a duration - 4h, 2d 4h, 1w. The deadline is that budget counted from the timer’s anchor. |
| End of next business day (NBD) | The deadline is the end of the next working day, according to the calendar in force for the issue. The budget is whatever working time remains until then, so it shifts with weekends, holidays and the calendar’s working hours. |
| DateTime field value | The deadline is read from a date or datetime field on the issue - a due date, a delivery date, a custom deadline. The budget is the working time between the anchor and that value, and it moves whenever someone edits the field. |
NBD and DateTime goals resolve to a point in time, while a Time String resolves to a duration. That difference shows up in the rules below.
Default goal
Every timer can have a default goal that applies to all issues unless overridden by a conditional goal.
| Field | Description |
|---|---|
| Goal | The goal itself - a Time String, End of next business day, or a DateTime field value (see Goal types). A Time String is a human-readable time expression; supported units: y (years), M (months), w (weeks), d (days), h (hours), m (minutes), s (seconds). Examples: 4h, 2d 4h, 1w, 30m. |
| Calendar | Optional. Use a specific calendar for this goal’s time calculation, overriding the field setting’s default calendar. |
| Calendar Field | Optional. Use a Calendar Select field for per-issue calendar override within this goal. |
How a goal decides the timer’s state
| Situation | Result |
|---|---|
| The resolved deadline is already in the past | The timer is Failed immediately. It does not wait for elapsed time to catch up with the goal. |
| The goal cannot be computed - the DateTime field is empty, or no working day can be resolved | The goal side is switched off: the timer keeps accumulating elapsed time, nothing can fail, and the goal-based display modes (LEFT_TIME, GOAL_TIME, FAILED_DATE) have nothing to show. |
| A stop event fires while no goal is in force | The timer ends as Completed, not Failed. |
The point the budget is measured from follows the field setting’s Calculate type: ALL_STARTS anchors the goal to the accumulated total across cycles, ONLY_FIRST_START to the first cycle, and ONLY_LAST_START to the most recent one. Changing Calculate type therefore moves the deadline, not just the displayed time.
Conditional goals (JQL-based)
You can define multiple goals with JQL conditions. The app evaluates goals in order and applies the first matching goal for each issue.
Each conditional goal has:
| Field | Description |
|---|---|
| Goal | The goal for this branch - any of the three goal types, same as the default goal. |
| JQL | A JQL condition that the issue must match for this goal to apply. |
| Calendar | Optional calendar override for this goal. |
| Calendar Field | Optional Calendar Select field for this goal. |
How matching works
For each issue, the app checks conditional goals in order:
- Evaluate Goal 1’s JQL against the issue → if match, use Goal 1
- Evaluate Goal 2’s JQL against the issue → if match, use Goal 2
- … and so on
- If no conditional goal matches, use the default goal
Example: Priority-based SLA
| Goal | JQL | Time |
|---|---|---|
| Goal 1 | priority = Highest |
1h |
| Goal 2 | priority = High |
4h |
| Goal 3 | priority = Medium |
8h |
| Default | - | 24h |
With this setup:
- Highest priority issues must be resolved within 1 hour
- High priority within 4 hours
- Medium within 8 hours
- Everything else within 24 hours
Goals are always re-evaluated
There is no setting that freezes a goal on an issue. Every time the timer is calculated, the app resolves the goal again: it re-runs the conditional goal JQL against the current issue data and falls back to the default goal if nothing matches. If the issue changes - a priority bump, a component added, a date field updated - the timer picks up the new goal on the next calculation, and the state (Running / Completed / Failed) is derived from that goal.
Earlier versions exposed an Allow Change Goal toggle for this. It has been removed; the re-evaluating behaviour is now the only behaviour.
Tips
- Goal order matters: conditional goals are checked in order. Put more specific JQL conditions first and broader ones later.
- Calendar per goal: different goals can use different calendars. For example, Highest priority may use a 24x7 calendar while Normal priority uses business hours only.
- Test goals: after configuring, run a recalculation and check a few sample issues to verify the correct goal is applied.
- JQL filter vs goal JQL: the field setting’s JQL Filter restricts which issues are processed at all. Goal JQL only determines which goal applies - the issue is still processed.

