It is possible for a custom field to have the same name as a built-in Jira system field; in which case, Jira will search for the system field (not your custom field). It is also possible for your Jira administrator to change the name of a custom field, which could break any saved filters that rely on that name. Custom field IDs, however, are unique and cannot be changed.
Queries run against the database are often highly repetitive and on the surface very cachable, but are not currently being cached. Highly repetitive and expensive queries, combined with the limits of vertical scalability, mean that options are being explored for scaling our usage of the database. When you have a project and issue type, you can retrieve the information for the issue fields by supplying the expand query parameter with the projects.issuetypes.fields value. To create an issue in Jira, you first need to specify a project and issue type. It is possible for your Jira administrator to change the name of a type, which could break any saved filter that rely on that name. Note, it is safer to search by priority ID than by priority name.
What are elements of a JQL query?
If the Stage 1 query is executed without permissions applied, then having access to see more or fewer issues is not a problem. While the SQL query that was generated was very large, for the customer in production that is using it, this JQL only takes 33ms to execute. What makes this JQL have high cost on database load is where and how it is executed.
You can search by request type name or request type description as configured in the Request Type configuration screen. Search for issues that belong to projects in a particular category. The “in” keyword will include any item that matches what are JQL queries and how to use them any item in the list. In the above example it will return all of the blocker and critical bugs in projects A, B, and C. The "WAS NOT" operator is used to find issues that have never had the specified value for the specified field.
A note on Jira and consistency
To create an issue, you will need to know certain key metadata, like the ID of the project that the issue will be created in, or the ID of the issue type. You can request the create metadata for all issue types across all projects by using the createmeta resource. Note, it is safer to search by custom field ID than by custom field name.
The "WAS IN" operator is used to find issues that currently have or previously had any of multiple specified values for the specified field. Measuring database load using execution time as an approximation does not account for one user being disproportionately affected by improvements. For example, user A could have a 50% improvement, but user B could have a 25% regression, for an average 12.5% improvement.
Request last activity time
Search for issues that belong to a particular epic in company-managed projects. The search is based on either the epic's name, issue key, or issue ID (i.e. the number that Jira automatically allocates to an issue). Search for issues where a particular custom field has a particular value. You can search by custom field name or custom field ID (i.e. the number that Jira automatically allocates to a custom field).
- He's been working on JQL Search Extensions leading the product and technical development.
- But if you want to tap into complex logic that is easily accessible, you’ll need functions.
- By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.
- We want to look through all the comments on the issue and add a little tooltip that will pop-up when you hover over a link to a Jira issue.
- Let’s take a look at how Jira Query Language, or JQL, can help solve the same problem with Jira Issues, which can similarly become unwieldy in large projects.
