Daniel Turczanski - JQL Search Extensions Atlassian Partner

@John Dunkelbergas always with complicated systems like Jira, you never know before you try. The large number of filters shouldn't be a problem by itself. I've seen people complaining about slow loading boards in case the filter contains too many projects. Might be worth starting a discussion about large number of filters…

Hi @Per Lindberg , 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…

If you have our JQL Search Extensions, you can run: issueFunction in childrenOfEpicsInQuery("project = ProjectX AND status != Invalid AND labels in (2022q1a,2022q1b)") Make sure to check out more examples here.

Hi @Kimberly Luttenbacher , please create a support request. It's the quickest way to get help with JQL Search Extensions. Thanks!

Hey @Matt Crozier We've added a support for the textarea fields based on your feedback. Can you mark my answer as an accepted solution? Thanks!

Hi @Andrey Ponomarenko Some functions are only available in our screen. Go to Apps->JQL Search Extensions->Extended Search and run your query there. Have a look at documentation here. It's best if you use the support channel to get a quick response from…

Make sure to follow the steps closely. Don't go to the filters view. The new JQL editor is currently available only in the Projects->Issues view.

Hey @Marat Kiniabulatov In this scenario, you shouldn't get PA-101 in the result. You query: issue in linkedIssuesOfQuery("project=RLS", "is caused by") should only match issues that are link to RLS with the specified link type. Can you create a support ticket so that we can troubleshoot your query? Make sure to provide…

Hi @Radha Krishna Singh, 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…

Hi @Dionei Piazza, 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…

Hi @Douglas Oliveira , 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…

Hi @Florian , 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 @Matt Crozier 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("File/Record", "*MFS_INIT*") Check out the…

Hi @Victor Crespo , 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 @Terry Zhang, You could get the report with JQL. 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…

You can use the new JQL editor that displays the users in a human readable format: * Go to any of your projects (choose Projects from the menu and open any project) * Click on Issues in the left-hand menu * Paste the JQL in the editor: assignee = ug:4d9d9df7-414a-402e-967d-995c01586224 

Hi @John Sawyer, 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 create a Jira filter and subscribe to it over email: commentLastCreatedOnDate < -1w Check out the documentation for more examples. I…

Hi @Munir Patel , The solution is to create the right quick filter in your Jira board. Quick filters are using JQL queries for filtering. 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 create…

Hi @David Kelman, As you're on Jira Cloud, the correct answer is to get an app that provides JQL extensions you're looking for. 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,…

Hi @Giulio Orombelli, With standard JQL, you can't get the subtasks based on their parents labels. 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: labels=MyLabel OR issue in…

Hi @Andrey Ponomarenko Standard JQL doesn't easily allow searching for exact words, special phrases and patterns. The error you see explains the limitations of native wildcard search. To get the wildcard support, use our professional indexing service JQL Search Extensions After you install the app, you can simply search:…

Try to replicate the board view with a JQL: filter="My board filter" and status changed to Done after -2w

Hi @kotha Eswar rao You can install our app JQL Search Extensions and get the results with: commentLastCreatedOnDate < -3d AND commentLastCreatedBy not in membersof(jsd-operators-staff) AND resolution is EMPTY You can see more examles in the article here. I hope this helps! Daniel

Hi @Marat Kiniabulatov, 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. I can see that you are already using our app: * JQL Search Extensions You can go to the Extended Search screen and run this query:…

Hi @johan.behl , Depending on your actual use case, a simpler solution may be to use JQL. Standard JQL doesn't easily allow it, but you can quickly find the children of epics with a custom field value using our professional indexing service JQL Search Extensions After you install the app, you can simply search: issue in…

Hi @Erica De Matteis , Standard JQL doesn't easily allow it, but you can quickly fetch the full epic-story-subtask hierarchy using our professional indexing service JQL Search Extensions After you install the app, you can simply search: issue in childrenOfIssuesInQueryRecursive("type=Epic and sprint='My sprint 1'") Check…

Hi @Elaine McMillan, With standard JQL and the linkedIssues function, you can only find the linked tickets if you know the exact issue keys. 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…

Hi @Ingo Mohr , If you have our JQL Search Extensions, you can create a scheduled daily or hourly rule to find the epics that need to be transitioned: type=Epic AND statusCategory="To Do" AND (issuesInEpicToDoCount>0 OR issuesInEpicInProgressCount>0) You can find more examples in the documentation. Thanks!

Hi @Jan Arve Dyrnes , 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 @kotha Eswar rao , An article about how to do it with our app can help. Chek it out here.