About fields

Time calculation functionality is based on three field types: Time in status, Stopwatch and Timer.

All these fields have the following functions:

• Working with data in real time - searching, sorting.
• Perform calculations using the work calendar and time zones of users.
• Suitable for queuing, monitoring, dashboards.
• They can be used in reports, exports, integration, and can be used to perform additional calculations (e.g., average project time).
• All fields have appearance and permissions settings.
• An unlimited number of fields and contexts can be created .
• They can calculate their values based on the request history. Can be used for both new/future and old tasks.
• Also for fields additional functions are available through auxiliary fields and field comparison.

Now about fields differences.

Time in status

Calculate the time spent in the specified status, statuses or status category. Serves for solving standard tasks of counting the time spent in the status .

It has simple configuration. For the field to start working, it is enough to specify the statuses and calendar for calculation after creation. However, the settings are sufficient to meet more complex requirements.

• 

• 

• Suitable for simple conditions of counting time: time spent in status or statuses.
• Does not allow to stop or start time counting by events (comment, value in field…). Only if the task changes status at these events.

Stopwatch

Calculate the time between events (actions) that occurred with the task . Very flexible settings allow you to calculate almost any time intervals in the life of the task. Fields can also be combined in calculations for extremely complex cases.

The settings are more complicated than for "time in status" field, but due to the flexibility and variety of settings, it allows you to calculate a huge number of scenarios.

• Calculates the time between events (issue creation, commenting, setting a value in fields, transition to a status …)
  • For example, start the report when creating an issue and stop when creating a comment for the author or transition to a status ‘in progress”
• Suitable for any time measurement. Large number of ready-to-use triggers available in the settings. Ability to start and stop stopwatches manually or via api.
• Can be configured to run with JQL condition. Runs automatically when a task matches a JQL request.
• Can send notifications on state change (on start, pause, …).
• Allows you to work not only with the calculated time but also with time in a pause state.

Timer

The field is implemented on the basis of the stopwatch and supplemented with a countdown function.
Limits are set on the basis of data in the task fields.

• You can specify that for an issue with a critical priority, the timer (for example, the reaction timer) should be set to 20 minutes. And for issues with a lower priority for 1 hour.
  

Calculates the difference (time remaining) between the goal time (limit) and the time between events (like a stopwatch).

• The issue must be commented within 30 minutes after creation. The timer when creating an issue will be set for 30 minutes and at the same moment will start counting down. The timer will stop the countdown at the moment of creating a comment and fix the value. If more than 30 minutes pass, the timer will show a negative value.

• Calculates time between events and shows how much time is left of the initial time(Goal time - time between events)
• Time limits (target time) are set by jql conditions.
• Allows to work not only with calculated time but also with the time in a pause state, remaining time and the time spent beyond the limits.

---

Get started

← Previous

User JQL help

Next →