AI Search for Jira
Search across issues, epics, sprints, and comments. Onyx indexes your Jira projects and answers questions about your team's work.
What were the original requirements for the payments feature?
The payments epic (PROJ-342) specified three requirements: Stripe integration for card payments, invoice generation for enterprise accounts, and usage-based billing support. The design doc is linked in the epic description.
PROJ-342 — Payments Epic
Your project history is locked inside Jira tickets
Your project history is locked inside Jira tickets
Jira holds years of project context: requirements, bug reports, sprint decisions, and implementation details. But finding specific information means crafting JQL queries or scrolling through backlogs.
Finding the original requirements for a feature means digging through epics and stories
Bug context and reproduction steps are buried in comment threads
JQL is powerful but most people don't know how to use it effectively
Cross-project search is clunky and requires switching between boards
How teams use Onyx with Jira
How teams use Onyx with Jira
Find feature requirements
Ask about a feature and get the original requirements from the epic, linked stories, and design discussions.
Bug history search
Search for similar bugs across all projects to find if an issue was reported before and how it was resolved.
Sprint and project context
Find what was shipped in a specific sprint, what got deprioritized, and the reasoning behind scope decisions.
Cross-project search
Search across all Jira projects in one query to find related work, dependencies, and duplicate issues without switching between boards.
Works great with
Works great with
Onyx searches across all your connected tools. Combine Jira with these connectors for unified AI search.
Connect Jira in under 5 minutes
Authorize Onyx with your Atlassian workspace. Onyx indexes issues, epics, comments, and attachments with project-level permission syncing.