Please note that JQL search statements listed below can be combined with other JIRA JQL statements.

Definition: Active Issue it is JIRA issue with timer started through "Automated Log Work" plugin.

All "date" values used as arguments in the below functions, start at the beginning of the day, e.g. "2017-06-28" is equal to "2017-06-28 0:00".

Table of contents:

JQL statements

activeIssues()

The below statement lists all issues with started timer.

issuekey in activeIssues()

activeIssues("username")

The below statement lists all issues with timer started for a given user.

issuekey in activeIssues("username")

activeIssuesStartedBefore("date")

The below statement lists all issues with timer started before 12am at given date.

issueKey in activeIssuesStartedBefore("2017-06-28")

This JQL function accepts also relative date format with plus "+" or minus "-" character at the beginning followed by JIRA duration. Allowed units are "y" (years), "M" (months), "w" (weeks), "d" (days) , "h" (hours) and "m" (minutes).

The below statement lists all issues with timer started before 12am four weeks ago.

issuekey in activeIssuesStartedBefore("-4w")

activeIssuesStartedBefore("date", "username")

The below statement lists all issues with timer started for a user before 12am at given date.

issueKey in activeIssuesStartedBefore("2017-06-28", "username")

This JQL function accepts also relative date format with plus "+" or minus "-" character at the beginning followed by JIRA duration. Allowed units are "y" (years), "M" (months), "w" (weeks), "d" (days) , "h" (hours) and "m" (minutes).

The below statement lists all issues with timer started for a user before 12am four weeks ago.

issuekey in activeIssuesStartedBefore("-4w", "username")

activeIssuesStartedAfter("date")

The below statement lists all issues with timer started after 12am at given date.

issueKey in activeIssuesStartedAfter("2017-06-24")

This JQL function accepts also relative date format with plus "+" or minus "-" character at the beginning followed by JIRA duration. Allowed units are "y" (years), "M" (months), "w" (weeks), "d" (days) , "h" (hours) and "m" (minutes).

The below statement lists all issues with timer started after 12am four weeks ago.

issuekey in activeIssuesStartedAfter("-4w")

activeIssuesStartedAfter("date", "username")

The below statement lists all issues with timer started for a user after 12am at given date.

issueKey in activeIssuesStartedAfter("2017-06-24", "username")

This JQL function accepts also relative date format with plus "+" or minus "-" character at the beginning followed by JIRA duration. Allowed units are "y" (years), "M" (months), "w" (weeks), "d" (days) , "h" (hours) and "m" (minutes).

The below statement lists all issues with timer started for a user after 12am four weeks ago.

issuekey in activeIssuesStartedAfter("-4w", "username")

activeIssuesTimerLowerThan("duration")

The below statement lists all issues with timer value lower than given duration.

issuekey in activeIssuesTimerLowerThan("4w 1d")

activeIssuesTimerLowerThan("duration", "username")

The below statement lists all issues with timer started for a user and value lower than given duration.

issuekey in activeIssuesTimerLowerThan("4w 1d", "username")

activeIssuesTimerGreaterThan("duration")

The below statement lists all issues with timer value greater than given duration.

issuekey in activeIssuesTimerGreaterThan("4w 1h")

activeIssuesTimerGreaterThan("duration", "username")

The below statement lists all issues with timer started for a user and value greater than given duration.

issuekey in activeIssuesTimerGreaterThan("4w 1h", "username")

activeIssuesTotalTimerLowerThan("duration")

The below statement lists all issues with any timer started and sum of all timers (from all users) lower than given duration.

issuekey in activeIssuesTotalTimerLowerThan("9w 1d")

activeIssuesTotalTimerLowerThan("duration", "username")

The below statement lists all issues with timer started for a user and sum of all timers for that issue (from all users) lower than given duration.

issuekey in activeIssuesTotalTimerLowerThan("9w 1d", "username")

User can have only one timer started for an issue so the above example gives the same result as the following one (because sum of timers for one timer equals value of that timer):

issuekey in activeIssuesTimerLowerThan("9w 1d", "username")

activeIssuesTotalTimerGreaterThan("duration")

The below statement lists all issues with any timer started and sum of all timers (from all users) greater than given duration.

issuekey in activeIssuesTotalTimerGreaterThan("7w 1d")

activeIssuesTotalTimerGreaterThan("duration", "username")

The below statement lists all issues with timer started for a user and its value greater than given duration.

issuekey in activeIssuesTotalTimerGreaterThan("3w 1d", "username")

User can have only one timer started for an issue so the above example gives the same result as the following one (because sum of timers for one timer equals value of that timer):

issuekey in activeIssuesTimerGreaterThan("3w 1d", "username")

Examples

All active issues in project "Demo"

issueKey in activeIssues() and project = Demo

All active issues for a given user in project "Demo"

issueKey in activeIssues("michael.smith") and project = Demo

Active issues in project "Demo" with timer started over 4 weeks ago

issuekey in activeIssuesStartedBefore("-4w") and project = Demo

Active issues with timer started last year

issuekey in activeIssuesStartedBefore("2017-01-01")

Active issues with sum of timers greater than 50 hours

issuekey in activeIssuesTimerGreaterThan("50h")

Resolved issues with active timer

issuekey in activeIssues() and status = Resolved

Browser not supported