Skip to main content

worklog

Overview​

The worklog function allows you to search for issues that have worklogs matching specific criteria, such as author, time period, or time spent.

Syntax​

issue in worklog("subquery", "author", "start_date", "end_date", "min_time_spent", "max_time_spent")

Parameters​

  • subquery (required): A valid JQL query that defines the set of issues to evaluate
  • author (optional): The display name of the worklog author
  • start_date (optional): The start date in format "yyyy/MM/dd HH:mm" or "yyyy/MM/dd", or a relative expression like -2w (see Relative date ranges)
  • end_date (optional): The end date in the same format as start_date
  • min_time_spent (optional): Minimum time spent (format: "1d 2h 3m 4s")
  • max_time_spent (optional): Maximum time spent (same format as min_time_spent)

Time Expression Format​

  • d - days
  • h - hours
  • m - minutes
  • s - seconds

Example: "1d 2h 30m" = 1 day, 2 hours, 30 minutes

Supported Operators​

  • in - issues matching the criteria
  • not in - issues not matching the criteria

Examples​

Finding issues with any worklogs​

issue in worklog("project = CITEST")

Finding issues with worklogs by a specific user​

issue in worklog("project = CITEST", "John Smith")

Finding issues with worklogs in a date range​

issue in worklog("project = CITEST", "", "2024/01/01", "2024/03/31")

Finding issues with worklogs of at least 1.5 hours​

issue in worklog("project = CITEST", "", "", "", "1h 30m")

Finding issues with worklogs of at most 2 hours​

issue in worklog("project = CITEST", "", "", "", "", "2h")

Finding issues with worklogs between 30 minutes and 2 hours​

issue in worklog("project = CITEST", "", "", "", "30m", "2h")

Relative date ranges (self-updating)​

The start_date / end_date arguments also accept a relative expression — a leading - followed by a duration — meaning "now minus that duration". Argon re-resolves the window every time the query runs (refreshed hourly), which is ideal for rolling timesheet-style dashboards.

-- Issues with time logged in the last week (a rolling weekly timesheet)
issue in worklog("project = CITEST", "", "-1w")

-- Time a specific user logged in the last 2 weeks
issue in worklog("project = CITEST", "John Smith", "-2w")

-- Substantial (2h+) work logged in the last 4 weeks
issue in worklog("project = CITEST", "", "-4w", "", "2h")

Note: the leading - is what makes a value relative. The date arguments use it (-1w = one week ago); the min_time_spent / max_time_spent arguments are plain durations with no minus (2h = two hours of logged time).

See Relative dates for the full format reference.

Performance Considerations​

  • The function analyzes all worklogs from issues matching the JQL subquery
  • Large numbers of worklogs may increase processing time
  • Use specific subqueries and date ranges to improve performance

Error Handling​

The function will return an error if:

  • Invalid date formats (must be "yyyy/MM/dd HH:mm" or "yyyy/MM/dd")
  • Invalid time expressions (must follow the format "1d 2h 3m 4s")
  • Negative time values
  • Minimum time spent greater than maximum time spent
  • Invalid JQL queries
  • commented - Search for issues with specific comment criteria
  • attachment - Search for issues with specific attachment criteria