šŸ“– How to create Timer and configure it step-by-step

In this guide we will create two timers that will track the time of the first response and time to resolution.

Time of the first response:
  • The time will be calculated according to the working calendar.
  • The timer will count 3 hours from the moment the task was created.
  • The timer will stop when answering or taking a task to work.
  • The timer can be paused by putting the task in Hold status.
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.

1. Create fields

  1. Create two timer field with names ā€œTime to first responseā€ and ā€œTime to resolutionā€.
  2. Set the screens and contexts on which you want to see the timer. We will configure the field in detail later.

2. Open All Timer Configs

go to {baseUrl}/secure/jibrokAllTimerConfigs.jspa

or open with admin search (gg + ā€œAll Timer Configsā€)

3. Click ā€œAdd timer configurationā€

Timers and Stopwatches - Scheme and configurations

Now we will configure the conditions for starting the timer, stopping ā€¦

4. Configure timer for ā€œTime to first responseā€

Configuration ā€œTime to first responseā€:

  1. Common settings
    • Set a name convenient for navigation - ā€œTime to first responseā€
    • Set Calculate type - ā€œFirst startā€. Our timer canā€™t restart.
    • Update goal with issue update - No. Our timer will always be set to 3 hours (only default time). Therefore, you can set any value.
    • Allow change goal after start - No. Our timer will only have a default time(goal). Therefore, you can set any value.
  2. Events
    • Start events:
      • The timer will start when the task is created. add ā€œIssue createdā€.
      • In our project the task can be transferred from another project. add ā€œIssue movedā€.
      • (see Pause events) When a task returns from Hold status, if it is still unanswered, then a timer must be started. add ā€œChange status from: Holdā€.
    • Pause events:
      • The team can send the task to hold the status without response. While the task in this status the timer needs to be stopped. add ā€œChange status to: Holdā€.
    • Stop events:
      • We record the response time when the user is given an answer.add ā€œCreate any public commentā€ or ā€œCreate first public commentā€.
      • We also fix the time when the task is taken to work or closed. add ā€œChange status to: In progressā€. add ā€œChange status to: Closedā€.
  3. Throw events We do not need Thrown events in this timer.
  4. Calendar 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.
    Work calendars
  5. Goal time
    • Default time (Default goal) - Time for which the timer is set if it is not possible to select the goal.
      • According to our condition the timer must be set for 3 hours. Set ā€œ3hā€
    • We do not need Additional goals in this timer.
    • Click ā€œSaveā€.

After create ā€œTime to first responseā€:

5. Configure timer for ā€œTime to resolutionā€

  1. Create new Configuration for (see p3)

  1. Common settings
    • Set a name convenient for navigation - ā€œTime to resolutionā€.
    • Set Calculate type - ā€œCalculate all start and create archiveā€. The timer may restart and I want to see its previous values.
    • Update goal with issue update - No. The priority of the task is determined at the time of adoption (before the timer starts). And in the future, priority cannot change.
    • Allow change goal after start - No. The priority of the task is determined at the time of adoption (before the timer starts). And in the future, priority cannot change.
  2. 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.)
    • 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ā€.
  3. throw events
    • We do not need Thrown events in this timer.
  4. Calendar
    • 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
  5. Goals
    • 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 and all tasks have priority. set ā€œ0ā€.
    • 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

Create goal:

  • JQL - condition by priority.
    • Example: priority = Lowest
  • Use default time? - No
    • Each goal has its own unique time.
  • Time - set by condition
    • Set ā€œ144hā€
  • Calendar - Set on which calendar you need to calculate the time. In this process, we use 1 working calendar.
    • Set ā€œDefaultā€
  • Sequence - The conditions for our purposes do not overlap, so we do not need this field(The field will be filled automatically after create goal)
    • You can leave this field blank.
  • Click ā€œCreateā€

After create first goal:

after create all goals click ā€œSaveā€

after create all goals:

after save config for ā€œTime to resolutionā€:

6. Open All timer schemes

go to {baseUrl}/secure/jibrokAllTimerSchemes.jspa

or open with admin search (gg + ā€œAll timer schemesā€)

7. Click ā€œAdd timer configuration schemeā€

Timers and Stopwatches - Scheme and configurations

Now you need to set which timer configurations to use depending on the project and the type of task. Analogue of context for custom fields.

8. Configure timer scheme for ā€œTime to first responseā€

  • Set a name convenient for navigation - ā€œTime to first responseā€
  • Projects - Select the projects for which this scheme will work.
  • Click ā€œAdd Associationā€
  • Set issue types and timer config(from p5)
  • Click ā€œCreateā€
    • We indicated that the timer config are relevant for tasks from the project and issue types.
  • Click ā€œSaveā€

Click ā€œAdd Associationā€:

Set issue types and timer config(see p5):

After save:

9. Configure timer scheme for ā€œTime to resolutionā€ (see p8)

In our case, the schemes differ only in name and selected timer config(Time to resolution)

After save:

10. Field settings for ā€œTime to first responseā€

Now we need to configure the fields and connect the created schemes to them.

Create timer field
Timers and Stopwatches - Scheme and configurations

  • Open the field settings (see screenshots) for field ā€œTime to first responseā€ (see p1)
  • Set timer scheme ā€œTime to first responseā€
    • Other settings can be set by default.
  • click ā€œSaveā€

Timer field Click configure:

Open timer field settings:

Set timer scheme:

Test

11. Field settings for ā€œTime to resolutionā€

(see p10) All the same, just select the scheme ā€œTime to resolutionā€

12. At this step, the basic setup is complete. You can test how everything works.

  • Create issue
  • The time report for the first answer began.

After create new issue:

13. Set status in progress

  • Time to first response - The timer has stopped.
    • In the current settings of the field, only time is displayed. The status of the timer can be displayed by hovering the mouse over the time.
  • Time to resolution - The timer has started.

14. Set status close or set resolution

Time to resolution - The timer has stopped.


šŸ“– Step by step - Time in status
Performance settings - JQL
JiBrok message field Message field
JiBrok time in status Time in status | SLA | Timer | Stopwatch
Tutorials
Settings
Work calendars
Time in status
Timers and Stopwatches
Stopwatch
Timer
Additional functions
Issue panels
Reports
Field Helpers
Other fields
API
Reference information
JiBrok Switch to User + Delegating SU (Jira) Switch to User + Delegating SU (Jira)
JiBrok time in status Time in status for Jira Cloud
Work calendars
Time in status fields
Issue panels
Reports
Service tools
Reference information
JiBrok Calculated fields Calculated fields (JBCF)
JiBrok Calculated fields Calculated fields (JBCF) for Jira Cloud
JBCF fields
Service tools
JiBrok Timer Timer field | SLA for Jira Cloud
Work calendars
Timer fields
Issue panels
Service tools
JiBrok Stopwatch Stopwatch for Jira Cloud
Work calendars
Stopwatch fields
Issue panels
Service tools
JiBrok Time between dates Time between dates for Jira Cloud
Time between dates fields
JiBrok Fields panel for Jira Service Management (JSM) Fields panel for Jira Service Management (JSM)
JiBrok Display Linked Issues Display Linked Issues
User helper for JiBrok cloud apps User helper for JiBrok cloud apps