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.
"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)
- āFirst responseā in failInDay () - find tasks that have expired or will expire on the āFirst responseā timer today
- ā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.