Jira Query Language enables anyone to build queries that can be executed in Jira to produce a set of results. These queries are very similar to SQL, GraphQL, and other query languages that enable easy access to large databases or data sets. The “CHANGED” operator is used to find issues that have a value that had changed for the specified field. The “WAS” operator is used to find issues that currently have or previously had the specified value for the specified field. This field is only available if time tracking has been enabled by your Jira administrator, and can only support the CONTAINS operator (“~”). Search for issues where the time spent is set to a particular value (i.e. a number, not a date or date range).
Find issues in projects where you have a specific permission. To search for a word like “customize” on an individual field, like the summary, use summary ~ “customize”. To jql contains perform a search of all text fields, use text ~ “customize”. What are JQL queries and how to use them For more examples, check out Advanced searching – fields reference.
Saving JQL Filters
For example, say your project has two SLAs that count Time to First Response. Some issues with this SLA use a 9am-1pm calendar, and others use a 9am-5pm calendar. If an agent starts work at 3pm, they probably want to work on issues from the 9am-5pm agreement first. They can use withincalendarhours() to find all the issues where Time to First Response is running at 3pm. One of the benefits of using JQL is that it saves time and effort by allowing users to quickly find the information they need.
“Tracked-only” requests are produced by integrations that stand separately from a change management process. These tools don’t respect approval or change gating strategies. Change requests that are “tracked-only” are just for record-keeping https://deveducation.com/ purposes. Search for issues that belong to projects in a particular category. If you used parentheses like in the following example, they wouldn’t have any effect, because the clauses enclosed in parentheses were already connected by AND.
JQL operators
This query would return the same results with or without the parentheses. You can set precedence in your JQL queries by using parentheses. Parentheses will group certain clauses together and enforce precedence. When you only use the OR keyword, all clauses will be treated as separate, and equal in terms of precedence. Don’t use the grouping character ‘(‘ at the start of a search query, as this will result in an error. For example, “(atlassian OR jira) AND bugs” will not work.
