Values are the actual data in the field under consideration. In the case of the ‘issue type’ field, values can be ‘bug’, ‘feature request’ etc. Oftentimes when you start searching your Jira issues, you can come back with A LOT of information. Scoping and sorting your queries will make it easy to see the exact information you need.
You can even create custom software that runs SQL queries to retrieve data and presents it in intuitive ways. Note, it is safer to search by resolution ID than by resolution name. It is possible for your Jira administrator to change the name of a resolution, which could break any saved filter that rely on that name.
If you prefer, by omitting the projectKeys and issuetypeNames parameters you can retrieve all the issue
field data at once for all projects and issue types. However, this approach could amount to a very large response and could
take some time to build on systems with a large number of projects and issue types. Data is one of the most valuable resources in the world right now, but the way it is stored and accessed can impact its efficiency and usability. Spreadsheets are a great way to store information until they become unwieldy, and even a basic lookup on such sheets might crash the system, let alone advanced search. When you have hundreds of columns and tens of thousands of rows, it’s much easier to use a database to store information and use Structured Query Language (SQL) to access the data.
“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 purposes. In a clause, a field is followed by an operator, which in turn is followed by one or more values (or functions). The operator compares the value of the field with one or more values or functions on the right, such that only true results are retrieved by the clause. This is extremely helpful for organizations that have service level agreements (SLA) with their customer base.
Winding Up Our Beginner’s Guide of JQL in Project Management
For example, as you search with an assignee, issues allocated to that particular assignee appear on the board. If you’re unfamiliar with Jira software, you can check out this video. It has insights that beginners need to know on how to use Jira for project management & activity tracking. This filters issues whose SLA cycle’s clock meets a specified time condition before the issue will breach an SLA goal. This filters issues where the SLA cycle is complete, meaning the issue has reached one of their stop events.
This is a basic example of how to create an issue using the Jira REST API. If an input file is required, it is denoted by the
–data @filename syntax and the file data is shown separately. In addition to built-in JQL, what are JQL queries and how to use them the Atlassian Marketplace contains plugins with advanced JQL functionality. The Full-Text Search Attachments for Jira Plugin, for example, enables JQL statements to search attachments for the name, type, and content.