The configuration is responsible for the timer operation algorithm: when should it start the countdown, when should it stop, for what time should it be started, and according to what working calendar should the time be counted.
⭐️Timers and Stopwatches - Schemes and configurations
-
Open {baseUrl}/secure/jibrokAllTimerConfigs.jspa
Or
gg + “Timer configs” - All timer configs are available in this interface. From here you can create, edit, and delete configurations.
- Click on button “Add timer configuration”
- Name - for navigation
- Calculate type - after the timer stops, in the event of a restart: The timer will not start, it will restart and delete the previous value, or it will be restarted and leave the previous values in the archive.
- First start - The timer will be started only once. It will not restart. After the timer stops, its value is completely fixed. The timer ignores restart events.
- Last start - The timer after restarting deletes its previous value. The timer always has one value that indicates the time of the last start.
- Calculate all start and create archive - The timer after each restart saves the current timer to the archive and starts a new countdown. If the timer is restarted several times, all values and resolutions of the timers are saved.
- Allow change goal after start - When the timer starts for the first time, it sets a target that is current at that time. When subsequent events are triggered, the target will be specified, which can lead to a recalculation of time.
- Update goal with issue update - The timer will respond to all changes in the issue and will refine the goal.
- Apply goal changes to - a further goal setting on the form: it selects what a change of the goal is applied to.
- Events - issue events to which the timer responds with a specific command. General information
- Throwable events - When an issue changes its state, the timer can generate a separate event.
- Notifications - the timer will send a notification when X% of the time has passed or X minutes are left until the end.
Deadline from a date field
As of 6.6 a goal - and the default goal - can take its deadline from a date field of the issue instead of a fixed time. In the goal form, pick the field under Deadline field:
- Due date, or
- any custom field of type Date Picker or Date Time Picker.
A goal with a deadline field needs no time string - leave the time empty. The goals table of the configuration shows the selected field next to the goal; a field that has since been deleted is shown as <id> (unknown), so you can find and fix the goals that point to it.
How the deadline is counted
| Situation | What the timer does |
|---|---|
| The field has a value | The goal time is the working time by the goal’s calendar from the start of the timer cycle up to the field value. A restart opens a new cycle, and the goal is counted again from its start. A pause pushes the deadline out, as for an ordinary goal. |
| The field value changes | The deadline is recalculated from the new value. This happens regardless of Allow change goal after start and Update goal with issue update - those flags decide which goal applies, not when its deadline is. |
| The date is already past when the cycle starts | The timer is breached (Failed) straight away. |
| A Date Picker field (a date without a time) | The deadline is the end of that day in the time zone of the goal’s calendar. |
| The field is empty | The goal does not match: the timer moves on to the next goal in order, or to the default goal. On the default goal an empty field means “no goal”. |
| The field is cleared after the timer started | The timer is not breached, and the remaining and overdue time is not written for JQL. |
| A goal with an inherited time, and the default goal has a deadline field | The goal takes its deadline from the default goal’s field. |
dateFieldId - duedate or customfield_NNNNN. See REST API.



