Subqueries

Subqueries is a new exciting feature that allows you to use more complex JQL in the cloud!

Checkout the dedicated documentation page here.

Related Issues

Related issues allow you to see other issues which are related to your work. It allows you to easily define which issues are related and where this information should be displayed.

Checkout the dedicated documentation page here.

Search extensions

Searching for attachments

Searching for subtasks

Searching for issues with subtasks 

Searching for comments 

Searching for versions

Links

Remote links

Updated

Searching for projects 

Field comparisons

Epic 

The following JQL extensions work on epics only

• issuesInEpicCount - search for epics with a particular number of child issues regardless of issue type
• bugsInEpicCount - search for epics with a particular number of bugs 
• storiesInEpicCount - search for epics with a particular number of stories 
• issuesInEpicToDoCount - search for epics with a particular number of child issues in "To Do" status category
• issuesInEpicInProgressCount - search for epics with a particular number of child issues in "In Progress" status category
• issuesInEpicDoneCount - search for epics with a particular number of child issues in "Done" status category
• bugsInEpicToDoCount - search for epics with a particular number of bugs in "To Do" status category
• bugsInEpicInProgressCount - search for epics with a particular number of bugs in "In Progress" status category
• bugsInEpicDoneCount - search for epics with a particular number of bugs in "Done" status category
• storiesInEpicToDoCount - search for epics with a particular number of stories in "To Do" status category
• storiesInEpicInProgressCount - search for epics with a particular number of stories in "in Progress" status category
• storiesInEpicDoneCount - search for epics with a particular number of stories in "Done" status category

Note on aggregation of dates

In case there are more than 100 timestamps to be stored for a particular date related JQL keyword the timestamps will be aggregated by day with time reset to start of the day (midnight). This means that the keyword won't be time sensitive, it will only be date sensitive for a particular Jira issue. 

This applies to the following keywords: 

• attachedOnDate
• updatedOnDates
• commentedOnDate
• commentUpdatedDate 

For example if the issue was updated 150 times over a course of 5 days, the updatedOnDates queries for that particular issue will see 5 timestamps for each day only.