In this guide we will create timer that will track the time to resolution.
Time to resolution:
- The time will be calculated according to the working calendar.
- The time it takes to resolve the request will depend on the priority of the task.
- Priority Lowest - 144h
- Priority Low - 72h
- Priority Medium - 36h
- Priority High - 18h
- Priority Highest - 9h
- The timer can be paused by putting the task in Hold status.
- The timer is fixed when you close the task or set the resolution.
- The timer restarts when the resolution is removed.
Open page for create fields
- In the top bar of the navigator there is a menu āAppsā in it you need to select the āTimer fieldā application. This will open the Application Settings menu.
- Then you need to go to the āTimer fieldsā tab
Create Timer/SLA for āTime to resolutionā
- Click to āCreateā for create new Timer.
- General information
- Provide a name for the timer. A field will be created with the specified name. This name will also be used in JQL queries.
- Set this field to active. Otherwise it will not work, it will only save the settings.
- Contexts
- Set Calculate type - āFirst startā.
- Events
- Start events:
- The timer will start when the task transition to āIn progressā. add āChange status to: In progressā.
- (see Pause events) When a task returns from Hold status, then a timer must be started. add āChange status from: Holdā.
- When a task is assigned (assignee change from Null(Empty) to user). add āassigned issueā.
- Restart events:
- If the task is removed from the resolution, then the timer starts the countdown again. add āRemove resolutionā. (If you do not need to restart the timer, then you need to use a pause instead of a retart.)
- āIt can be omitted if you are only interested in the time of the first decision of the query (Calculate type - āFirst startā.). There will soon be new types to handle cases where requests are re-submitted. If you are interested in the total time, then you need to use the āPauseā events to pause the calculation. After triggering āStopā, the calculation is terminated completely.
- If the task is removed from the resolution, then the timer starts the countdown again. add āRemove resolutionā. (If you do not need to restart the timer, then you need to use a pause instead of a retart.)
- Pause events:
- The team can send the task to hold the status. While the task in this status the timer needs to be stopped. add āChange status to: Holdā.
- Stop events:
- We fix the timer time when the task closes or a solution is established for it. .add āChange status to: Closedā. add āSet resolutionā.
- Start events:
- Display settings
- Time settings
- Default calendar - You can set a working calendar by which the timer will be considered. If left blank, the time will be considered 24/7
- Default time (Default goal) - Time for which the timer is set if it is not possible to select the goal.
- The timer time depends on the priority. If the issue does not have a priority or it does not match any of the conditions, then the default target 0 will be selected. A zero target does not start the timer.
- The target time will be determined by the priority of the task. For each condition (priority) you need to add a goal.
- Create goals by priorities: see screenshots
- JQL - Condition for the application of this Goal. If none of the conditions match the issue then the default goal will be applied.
- Time option:
- Time - You can specify the time manually. After the start, the timer will be set to the specified time.
- Date time field - The timer will count down the time from the start to the date in the specified issue field.
- Preset options:
- NBD (Next business day) - The timer will count down the time from the moment of the start to the end of the next working day.
- An example of a combination of different conditions:
Goals and conditions for ātrack the time to resolutionā
- Click āSaveā
- After a successful save, the data synchronization process will start. It includes calculating historical values and starting tracking of active timers. Depending on the number of requests, the first synchronization may take some time. You can follow the synchronization status in the āService infoā tab.
- After you create the field, you can go to the āStart Pageā tab. The examples will be updated on it and there will be links to demo JQL queries.
- You can also work with this field as with any other. You can display it on screens, in reports, search and sort data by it.
- The data in the field will be updated periodically and whenever the task is updated. The frequency of automatic updates is now automatically detected. The less time is left, the more frequent updates will be.
- Current intervals of time updates:
- 1-5min: every 1 min
- 5min-2h: every 5 min
- 2h-12h: every 15 min
- 12h-24h: every 30 min
- 24h-7d: every 1h
- 7d-14d: every 2h
- 14d+: every 4h
- Current intervals of time updates: