JQL Functions
Argon provides 17 custom JQL functions that enhance Jira's native query capabilities. These functions allow you to query issues based on relationships, history, time tracking, and content that standard JQL cannot express.
Function Categories
Links and Hierarchy
Query issues based on their relationships with other issues.
| Function | Description |
|---|---|
| linkedByQuery | Find issues linked to by issues matching a query |
| linksQuery | Find issues linked from issues matching a query |
| childrenOf | Find children of issues matching a query |
| parentOf | Find parents of issues matching a query |
Field Operations
Compare and count field values across issues.
| Function | Description |
|---|---|
| fieldValue | Compare field values across issues |
| fieldCount | Filter by count of field values or properties |
| regex | Match field values using regular expressions |
Math Functions
Perform statistical calculations on numeric fields.
| Function | Description |
|---|---|
| min | Compare against minimum value |
| max | Compare against maximum value |
| avg | Compare against average value |
Time Functions
Query based on time spent in statuses.
| Function | Description |
|---|---|
| timeInStatus | Find issues by time spent in a status |
| timeExpression | Convert time expressions for comparisons |
History Functions
Search issue change history.
| Function | Description |
|---|---|
| changedBy | Find issues with field changes |
| transitionedBy | Find issues transitioned to a status |
Activity Functions
Search comments, attachments, and worklogs.
| Function | Description |
|---|---|
| commented | Find issues with matching comments |
| attachment | Find issues with matching attachments |
| worklog | Find issues with matching worklogs |
Common Parameters
Most functions share common parameter patterns:
Subquery
All functions accept a subquery parameter - a valid JQL query that defines the scope of issues to evaluate.
issue in linkedByQuery("project = DEV AND status = Done")
Date Format
Functions that accept dates use the format yyyy/MM/dd or yyyy/MM/dd HH:mm:
issue in changedBy("project = DEV", "Status", "2024/01/01", "2024/03/31")
Time Expressions
Functions that accept time expressions use the format Xw Xd Xh Xm Xs:
issue > timeInStatus("project = DEV", "In Progress", "2w 3d")
Operator Support
| Operators | Functions |
|---|---|
in, not in | linkedByQuery, linksQuery, childrenOf, parentOf, regex, changedBy, transitionedBy, commented, attachment, worklog |
=, !=, >, >=, <, <= | min, max, avg, timeInStatus, fieldCount |
=, !=, >, >=, <, <=, in, not in | fieldValue |