Daniel Turczanski - JQL Search Extensions Atlassian Partner

Hi @Mateusz Zurawik-Le Mercier , With standard JQL, you can only get a list of issues and export them to Excel for further processing. This works if you want to do a one-off analysis. If your use case is more dynamic than that, look beyond standard Jira. Standard JQL doesn't easily allow it, but you can quickly find the…

Hi @Arevik Hakobyan feel free to get in touch and I can show you how the app can solve your problems and help you to decide if you need the app at all. Thanks!

Hi @Arevik Hakobyan, Standard JQL doesn't easily allow it, but you can quickly find the results using our professional indexing service JQL Search Extensions After you install the app, you can simply search: issue in childrenOfIssuesInQueryRecursive("key in (THEME-1, THEME-2, THEME-3)") and type=Story and status="To do"…

You may consider the service desk solutions described in our app's documentation as they don't require complex automation rules.

Hi @Daniel Hernández Standard JQL doesn't easily allow searching for exact words, special phrases and patterns. To get the wildcard support, use our professional indexing service JQL Search Extensions After you install the app, you can simply search: issue in wildcardMatch("summary", "[SEO-*]") Check out the documentation…

Hi @a.savchyn , With standard JQL, you can only get a list of issues with links and export them to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can find the results quickly using our professional indexing service JQL Search Extensions After you…

Hi @[deleted] , With standard JQL, you can only get a list of issues with links and export them to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can find the results quickly using our professional indexing service JQL Search Extensions After you…

Hi @Sergii Shevchuk , With standard JQL, you can only get a list of issues with links and export them to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can find the results quickly using our professional indexing service JQL Search Extensions…

Hi @Anna , With standard JQL, you can only get a list of issues and export them to Excel for further processing. This works if you want to do a one-off analysis. If your use case is more dynamic than that, look beyond standard Jira. Standard JQL doesn't easily allow it, but you can quickly find the results using our…

Hi community! This is an old question but I'm sure this answer is helpful today. With standard JQL, you can only get a list of issues and export them to Excel for further processing. This works if you want to do a one-off analysis. If your use case is more dynamic than that, look beyond standard Jira. Standard JQL doesn't…

Hi @Vasilescu Elena , With standard JQL, you can only get a list of issues with links and export them to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can find the results quickly using our professional indexing service JQL Search Extensions…

How about: status=Review and status changed BEFORE 3d and updated<-3d

Your first example is probably searching through all the text fields and not only the summary. Try this JQL: project = HEL AND text ~ "FW: CSSP" ORDER BY created DESC Note that I replaced "summary" with "text".

Hi @Evert Morren Yes, it's possible in most cases. You need to save the query as a Jira filter and use the filter in the automatino rule. Feel free to contact our support and we can help.

Hi @hisham Osman , With standard JQL, you can only get a list of issues and export them to Excel for further processing. This works if you want to do a one-off analysis. If your use case is more dynamic than that, look beyond standard Jira. Standard JQL doesn't easily allow it, but you can quickly find the results using…

Hi @Metod Bulovec , Standard JQL doesn't easily allow it, but you can find the results quickly using our professional indexing service JQL Search Extensions. After you install the app, you can simply search: issue in childrenOfIssuesInQueryRecursive("'Billable[Dropdown]' = Yes") Check out the documentation to see more…

Hi @dennis.werner , Standard JQL doesn't easily allow searching for exact words, special phrases and patterns. To get the wildcard support, use our professional indexing service JQL Search Extensions After you install the app, you can simply search: issue in wildcardMatch("description", "XXXX*") Check out the documentation…

Hi, With standard JQL, you can only get a list of issues with links and export them to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can find the results quickly using our professional indexing service JQL Search Extensions After you install the…

Hopefully, it solves your problem. You can always contact our support and we can help with specific requirements and queries.

Sure, if you're able to work around your problem without an app, please let us know here.

Hi @[deleted] , With standard JQL, you can only get a list of issues that belong to closed, open, or future sprints - regardless of the board they belong to. You can also export the issues to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can…

If the options follow a pattern, you may find our regex JQL function handy to filter out issues with additional options. It's part of JQL Search Extensions.

Try using this JQL clause to filter out the subtasks: issuetype not in subTaskIssueTypes()

You may be interested in our commentLastUpdatedOnDate JQL alias. You can find issues that were recently commented on and order them by the comment date: commentLastUpdatedOnDate < -2d order by commentLastUpdatedOnDate desc It's part of JQL Search Extensions.

Hi @faisal khan, With standard JQL, you can only get a list of issues with links and export them to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can find the results quickly using our professional indexing service JQL Search Extensions After…

A lot of project managers end up using our JQL function childrenOfIssuesInQueryRecursive in a setup like that. Just keep in mind it's there once you need it.

Hi @[deleted] , With standard JQL, you can only get a list of issues that belong to closed, open, or future sprints - regardless of the board they belong to. You can also export the issues to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can…

Hi @Albert Arul Prakash Rajendran , With standard JQL, you can only create static queries that use the hard-coded issue keys. This works fine if you want to do a one-off analysis. If your use case is more dynamic than that, look beyond standard Jira. Standard JQL doesn't easily allow it, but you can quickly find the…

Hi @bela shaji , With standard JQL, you can only get a list of issues that belong to closed, open, or future sprints - regardless of the board they belong to. You can also export the issues to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can…

Hi @Shirley , With standard JQL, you can only get a list of issues that belong to closed, open, or future sprints - regardless of the board they belong to. You can also export the issues to Excel for further processing. This works if you want to do a one-off analysis. Standard JQL doesn't easily allow it, but you can find…