Jira search can provide valuable project insights and answer questions that are important to the team. The advanced search feature is the most powerful and flexible way to find issues in Jira. You can use the Jira Query Language (JQL) to specify criteria that cannot be defined in quick or basic searches.
Advanced search allows users to create structured queries using JQL to locate issues both within individual projects and across multiple projects. The results from these queries can be saved and used as filters and views throughout Jira, including on boards.
Required knowledge
This page requires some knowledge of searching for issues using JQL. It has been described in the original Atlassian documentation. Please click here to get more information on querying for issues. Due to the Issue Navigator limitations, it's not possible to search for the SLAs in the Basic mode.
SLA PowerBox for Cloud provides a set of functions you can use to track performance against your SLAs. This page lists the SLA-specific JQL functions you can use to query the SLA data in your issues, as well as some examples of creating common JQL queries on SLA Metrics.
Each function listed below searches for the current SLA metric's data. Historical cycles are not searchable; for example, you cannot search for issues that were paused in the past but are currently active.
Search functions
Each function listed below utilizes the name of SLA metric you are searching for.
| Function | Description | Example |
|---|---|---|
slaMetricState("", "") | returns issues with SLA metric in a defined state | issue in slaMetricState("SLA metric", "Active") |
slaMetricBreached("") | returns issues with breached SLA (regardless of current metric state) | issue in slaMetricBreached("SLA metric") |
slaMetricDeadline("", "", "") | returns issues that match a specified deadline criteria Date format: "YYYY/MM/DD hh:mm" Supported operators: =, !=, <, <=, >, >= Supported functions: now(), now(-1d), startOfDay(), startOfMonth(), startOfWeek(), startOfYear(), endOfDay(), endOfMonth(), endOfWeek(), endOfYear(). | issue in slaMetricDeadline("SLA metric",">", "startOfWeek()") issue in slaMetricDeadline("SLA metric","<", "now()") issue in slaMetricDeadline("SLA metric","<", "2024/11/07 15:30") |
Flowing deadline
In case of SLA metric being paused ("On Hold"), the actual deadline is unknown at the moment because it is moving forward (as the time on hold is not included in the Time spent). This is what could be called "flowing deadline".
By default, the issues where the SLA metric is On hold are not included in the search results of slaMetricDeadline("", "", "") function. It works this way because ignoreFlowingDeadline flag is set as 'True' by default.
However, the issue with the paused SLA metric can be included in the search result if ignoreFlowingDeadline flag is set to 'false'. To do so, you will have to add one more argument to the SLA deadline search function: issue in slaMetricDeadline("SLA metric 1.0","<", "2024/11/07 23:50", "false").