Is JQL too complicated to learn and use to get the results you want? We're thrilled to announce the beta release of the new AI JQL Fixer, designed to simplify your Jira experience by using AI to correct your JQL mistakes.
The JQL Fixer leverages AI to help you correct minor syntax errors in your JQL queries. This tool enhances the experience for users who depend on JQL to search for issues, enabling you to efficiently locate your results and proceed with your tasks seamlessly.
We'd love to hear your thoughts and feedback as we continue to refine the JQL Fixer. Your input is invaluable in helping us create tools that empower you to work more efficiently.
We encourage you to pop a message in the comments down below, or you can reach out to me to provide feedback at lzhu2@atlassian.com.
The AI JQL Fixer is exclusively available to all AI-enabled Jira Cloud Premium and Enterprise customers when searching with JQL.
If you're not on these plans but are interested in trying out this feature, consider upgrading to https://www.atlassian.com/software/jira/premium or https://www.atlassian.com/software/jira/enterprise.
If you are on these plans but still don’t see these features, you may need to enable AI features, or to contact your admin to do so.
You can also find out more about Atlassian Intelligence features in Jira here and understand how Atlassian Intelligence handles your data here.
Awesome! this will help our users alot.
I can not see it in our site - how to enable beta view?
@Martin Vali - Atlassian Intelligence / AI features need to be enabled to view this. I checked in my instance and we have AI features enabled in Jira, so I'm able to use this AI JQL Fixer function.
@Dave Buitenhek it was enabled , still gouldn't see. Now it's there, Thanks
The idea is good however suggestions should focus on the actual problem not add additional JQL elements. In this article example it adds ORDER BY automatically even someone just typed query with assignee without ORDER BY (which should also work)..
In addition it should also somehow visually point exactly where the problem is (since currentUser() was fine) and educate users. I mean error says that problem is with assignee so after suggesting query it should give a message that "assignee" is the field that should be used..
It looks like you're new here. Sign in or register to get started.
