The configuration is responsible for the stopwatch operation algorithm When should he start the countdown, when should he stop, for what time should he be started, according to what working calendar should the time be counted.
⭐️Timers and Stopwatches - Schemes and configurations
gg + “Stopwatch configs”
All stopwatch configs are available in this interface. From here you can create, edit and delete config.
*Click on button “Add stopwatch configuration”
- 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. It will be restarted and leave the previous values in the archive.
- Allow change goal after start - When the timer starts for the first time, it sets a target that is current at the current time. When subsequent events are triggered, the target will specify, which can lead to a re-calculation of time.
- Update goal with issue update - The timer will respond to all changes in the task and will refine the goal.
- Events - issue events to which the timer responds with a specific command. General information
- Throwable events - When a issue changes its state, the timer can generate a separate event.
- JQL - if no jql is specified, then the timer will start when start is triggered. Otherwise, it will only start if it matches at least one jql.