{"id":1529,"date":"2022-01-19T20:49:34","date_gmt":"2022-01-19T20:49:34","guid":{"rendered":"https:\/\/mgfacade.com\/?p=1529"},"modified":"2023-11-10T14:41:04","modified_gmt":"2023-11-10T14:41:04","slug":"use-advanced-search-with-jira-query-language-jql","status":"publish","type":"post","link":"https:\/\/mgfacade.com\/?p=1529","title":{"rendered":"Use advanced search with Jira Query Language JQL Jira Work Management Cloud"},"content":{"rendered":"

You can even build your own plugins with Java, JavaScript, CSS, and HTML skills. Now, check the following development fields that can be used in JQL queries. You can search by status name or status ID (i.e. the number that Jira automatically allocates to a status).<\/p>\n

\"what<\/p>\n

You could narrow your search for issues that are not closed in the current sprint AND that were previously assigned to another sprint. This would tell you how many issues were out of scope in the last sprint and couldn\u2019t be completed. Even the Roadmap Portal for Jira Service Desk add-on is based on JQL which helps gather feedback and votes from your Jira service desk customers. These tools help in automating important but routine aspects of the software development life cycle, freeing up valuable time for managers and developers.<\/p>\n

Assignee<\/h2>\n

You can search by resolution name or resolution ID (i.e. the number that Jira automatically allocates to a resolution). Search for issues where the remaining estimate is set to a particular value (i.e. a number, not a date or date range). You can search by priority name or priority ID https:\/\/deveducation.com\/<\/a> (i.e. the number that Jira automatically allocates to a priority). Search for issues where the original estimate is set to a particular value (i.e. a number, not a date or date range). For example, add a red stripe to issues that have some blockers, and keep all other issues green.<\/p>\n

\"what<\/p>\n

The advanced search allows you to build structured queries using the Jira Query Language (JQL) to search for issues. You can specify criteria that you can’t define in the quick or basic searches. For example, you can use the ORDER BY clause in JQL when you\u2019re searching for issues. JQL can help gain key project insights and help you find not just issues but also important information in projects.<\/p>\n

JQL Add-Ons<\/h2>\n

Thanks for sharing this article @Andrei Pisklenov _Actonic_ ! This is really very useful for any new Jira users looking for learning JQL search capabilities in Jira. Find issues whose summary or description contain any of the listed words in a test project.<\/p>\n

\"what<\/p>\n

So you could just start with a wide search and narrow down from there. Although Jira JQL is pretty good at narrowing down from huge piles of issues, sometimes your query will jql does not contain<\/a> still return a volume of issues that\u2019s simply too large. For this example, let\u2019s say we want to find all issues that are urgent and not done within a specific Epic link.<\/p>\n

Overview of Jira Query Language Interface<\/h2>\n

The values are specified as a comma-delimited list, surrounded by parentheses. You\u2019ll explore commonly used functions that add flexibility to your searches, and how parentheses adjust the operation of functions. You\u2019ll also understand the intricacies of searching with text-based fields and dates. When you put the pieces together, you\u2019ll have everything you need to create complex search queries for any criteria you wish. Search for issues that have merged pull requests on linked Bitbucket instances. Note that this query will also return issues with declined requests.<\/p>\n