<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/296aaeed7af640c6850a96d9c3906e95&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/296aaeed7af640c6850a96d9c3906e95-03d804b1e955517d.gif</thumbnail_url><duration>2725.24</duration><title>Natural Language to JQL - New improvements including Custom Field search</title><description>The meeting focused on enhancing Jira&apos;s Issue Search through JQL and AI, addressing user challenges, and introducing Atlassian&apos;s AI tool, Rover. Key improvements include Natural Language to JQL, error reduction, and user feedback integration. Future plans involve expanding AI capabilities to AQL, with upcoming demos at a team conference.

### Introduction and Agenda Overview 2:22

- Matt Burton introduced the session as part of the &quot;How We Built This&quot; series, focusing on making Issue Search effective.
- The session aimed to cover Jira Query Language (JQL), Natural Language to JQL, maximizing Issue Search, and Atlassian&apos;s AI tool, Rover.
- The presentation was structured to include a Q&amp;A session at the end, with an expected duration of 30 to 45 minutes.

### Jira Query Language (JQL) Overview 4:58

- JQL is essential for searching issues in Jira, interfacing with multiple databases.
- The issue search UI has undergone design changes, including renaming &quot;issue&quot; to &quot;work items.&quot;
- JQL consists of fields, operators, and values, forming clauses and queries.
- Despite its complexity, JQL is crucial for detailed searches, though 93% of users avoid it due to its complexity.
- Basic search is limited, prompting the development of Natural Language to JQL.

### Natural Language to JQL 9:33

- Natural Language to JQL converts natural language queries into JQL, available only on cloud with AI enabled.
- The feature has improved from generating valid JQL 65% of the time in 2023 to nearly 99% recently.
- Despite improvements, user retention for AI-powered search is lower compared to basic and advanced searches.
- The feature is being refined to enhance user experience and retention.

### Limitations and Feedback on JQL 20:50

- JQL&apos;s main limitation is its inability to easily explore issue hierarchies, such as searching for child issues.
- Users cannot compare fields between issues, a common request.
- Third-party plugins offer some solutions, but Atlassian does not provide these features out-of-the-box.
- User feedback is actively monitored to guide improvements.

### Tips for Effective Issue Search 24:12

- Users are encouraged to use JQL or Natural Language to JQL for complex searches.
- A new JQL debugger feature is in beta, expected to be available next month.
- Managing searches within a project scope can enhance search relevance.
- The text field in JQL allows for comprehensive text searches across text-based fields.
- Community resources and documentation are recommended for learning and troubleshooting JQL.

### Introduction to Rover 29:24

- Rover is Atlassian&apos;s AI offering, integrating language models to enhance data interaction.
- It allows for multi-turn interactions and can chain product features for deeper data exploration.
- Rover can perform actions like summarizing issues and assigning tasks, enhancing workflow efficiency.
- The tool supports integration with various third-party data sources, expanding its utility.

### Future Developments and Q&amp;A 39:44

- Arielle Unterberger inquired about plans for AQL development similar to JQL.
- Matt Burton confirmed internal testing for NL to AQL, with plans to integrate it into Rover.
- Upcoming demos are expected at a team conference in the near future.
- Participants were encouraged to provide feedback and reach out with questions via email or feedback tools.</description></oembed>