Timer - JQL

Functions take the following parameters.

  • condition - one of the characters <, <=, => =,>. For example: ā€œ>ā€.
  • calendar - the name or id of the calendar. For example: ā€œSupportā€ or ā€œ1ā€. How to view calendars?
  • stopwatch config id and stopwatch scheme id - number. Jira admin can view it.
  • time - time string corresponding to one of the patterns.
"5h35m12s" - 5 hours 35 minutes 12 seconds
"5h12s" - 5 hours 12 seconds
3000m - 3000 minutes
"0", "0s" ... - time is zero.

Search works through the field. Therefore, all JQLs begin with the field name.

Search functions in the ā€œTimerā€ field.

Work when search engine is connected Search Templates

JQL Functions

ā€œTimer fieldā€œ in active()

  • Returns tasks that have a timer is running

  • If the timer uses a calendar, the field may indicate that it is not working hours. This does not affect the search if timer is running.

ā€œTimer fieldā€œ in inactive()

  • Returns tasks that have a timer is pause, failed or completed.

ā€œTimer fieldā€œ in isCompleted()

  • Returns tasks that have a timer is completed. Those the timer is stopped and the time has not yet ended.

ā€œTimer fieldā€œ in isFailed()

  • Returns tasks that have a timer is failed. Those the timer is stopped and the time has ended.

ā€œTimer fieldā€œ in isPaused()

  • Returns tasks that have a timer is paused. Breaks in the work calendar are not considered a pause. But can be displayed in the field as a pause.

ā€œTimer fieldā€œ in isRunning()

  • Returns tasks that have a timer is running. A break in the working calendar does not affect the search. The timer may be in state running, but at the same time the field will be displayed as a pause state.

ā€œTimer fieldā€ in timeSpent(ā€œconditionā€, ā€œtimeā€)

  • Returns tasks for which the timer has already counted the specified time. Those. The timer was active(in state Running) for the specified time.

ā€œTimer fieldā€ in realTimeSpent(ā€œconditionā€, ā€œtimeā€)

  • Returns tasks for which the timer has already counted the specified time. Those. The timer was active(in state Running) for the specified time.
  • The function works in real time.
  • It has a limit on the size of the issue.
  • The function is suitable for sampling active counters. Real-time reporting, work queues of tasks with reference to reaction time, execution ā€¦

ā€œTimer fieldā€ in timeLeft(ā€œconditionā€, ā€œtimeā€)

  • Returns tasks for which the remaining timer time matches the condition.
  • The function works in real time.
  • It hasnā€™t a limit on the size of the issue.
  • The function is suitable for sampling active counters. Real-time reporting, work queues of tasks with reference to reaction time, execution ā€¦

Search by date

  • ā€œfield nameā€ in startInDay(ā€œnumberā€) - Search for issues by the day when the timer was first started.
  • ā€œfield nameā€ in startInWeek(ā€œnumberā€) - Search for issues by the week when the timer was first started.
  • ā€œfield nameā€ in startInMonth(ā€œnumberā€) - Search for issues by the month when the timer was first started.

  • ā€œfield nameā€ in stopInDay(ā€œnumberā€) - Search for issues by the day when the timer was stopped.
  • ā€œfield nameā€ in stopInWeek(ā€œnumberā€) - Search for issues by the week when the timer was stopped.
  • ā€œfield nameā€ in stopInMonth(ā€œnumberā€) - Search for issues by the month when the timer was stopped.

  • ā€œfield nameā€ in failInDay(ā€œnumberā€) - Search for issues by the day when the timer was failed.
  • ā€œfield nameā€ in failInWeek(ā€œnumberā€) - Search for issues by the week when the timer was failed.
  • ā€œfield nameā€ in failInMonth(ā€œnumberā€) - Search for issues by the month when the timer was failed.

  • ā€œfield nameā€ in pauseInDay(ā€œnumberā€) - Search for issues by the day when the timer was paused.
  • ā€œfield nameā€ in pauseInWeek(ā€œnumberā€) - Search for issues by the week when the timer was paused.
  • ā€œfield nameā€ in pauseInMonth(ā€œnumberā€) - Search for issues by the month when the timer was paused.

  • Examples:
    • ā€œFirst responseā€ in failInDay () - find tasks that have expired or will expire on the ā€œFirst responseā€ timer today
      • ā€œFirst responseā€ in failInDay (ā€œ-1ā€) - find tasks that have run out of time by the ā€œFirst responseā€ timer yesterday (1 day ago)
      • ā€œFirst responseā€ in failInDay (ā€œ-7ā€) - find tasks for which the ā€œFirst responseā€ timer has expired a week ago (7 days ago)
      • ā€œFirst responseā€ in failInDay (ā€œ7ā€) - find tasks that have expired or will expire on the ā€œFirst responseā€ timer in a week (after 7 days)
  • ā€œfield nameā€ in searchByStartDate(ā€œconditionā€, ā€œdateā€) - Search for issues by the date when the timer was first started.
  • ā€œfield nameā€ in searchByPausedDate(ā€œconditionā€, ā€œdateā€) - Search for issues by the date when the timer was last paused.
  • ā€œfield nameā€ in searchByStopDate(ā€œconditionā€, ā€œdateā€) - Search for issues by the date when the timer was stopped.
  • ā€œfield nameā€ in searchByFailDate(ā€œconditionā€, ā€œdateā€) - Search for issues by the date when the timer was failed.

  • date is a string with a date in the format ā€˜yyyy-MM-ddā€™ or ā€˜yyyy-MM-dd HH: mmā€™
  • Examples:
    • ā€œFirst responseā€ in searchByStartDate (ā€œ>ā€, ā€œ2021-01-01ā€) - tasks for which the timer started after ā€œ2021-01-01ā€
  • ā€œfield nameā€ in startInDateRange (ā€œdateā€, ā€œdateā€) - Search for issues by the date when the timer was started (duration).
  • ā€œfield nameā€ in stopInDateRange (ā€œdateā€, ā€œdateā€) - Search for issues by the date when the timer was stopped (duration).
  • ā€œfield nameā€ in failInDateRange (ā€œdateā€, ā€œdateā€) - Search for issues by the date when the timer was failed (duration).

  • Examples:
    • ā€œFirst responseā€ in failInDateRange (ā€œ2020-01-01ā€, ā€œ2021-01-01ā€) - tasks whose timer has exceeded its time during 2020.

ā€œTimer fieldā€ in searchByCalendar(ā€œcalendarIdā€)

  • Returns tasks whose timer uses the specified attribute.

ā€œTimer fieldā€ in searchByGoal(ā€œgoalIdā€)

  • Returns tasks whose timer uses the specified attribute.
  • Id can be found with Jira admin.

ā€œTimer fieldā€ in searchByTimerConfig(ā€œtimerConfigIdā€)

  • Returns tasks whose timer uses the specified attribute.
  • Id can be found with Jira admin.

ā€œTimer fieldā€ in searchByTimerScheme(ā€œtimerSchemeIdā€)

  • Returns tasks whose timer uses the specified attribute.
  • Id can be found with Jira admin.

Timer - fields settings
Templates for field values
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