Skip to main content

Ticket Discovery

The Dashboard (/) is where AI-assisted test generation starts. You search for tickets, review acceptance criteria, and generate BDD scenarios and test cases — all without leaving the page.

Discovery page — search bar with Keyword / Load by IDs / Ask AI tabs and connector selector in the top bar

Search modes​

Type a phrase and press Enter. QA Hub queries your active ticket source and returns matching open issues.

Load by ID​

Enter one or more ticket keys separated by commas:

PROJ-42, PROJ-43, PROJ-50

All tickets are fetched and displayed together. Useful when you have a known sprint list.

Describe what you need in plain language:

"login and session management edge cases"

QA Hub extracts the intent and searches the ticket source automatically, surfacing relevant stories you might otherwise miss.

Ticket card​

Each result shows:

  • Key and title (e.g., PROJ-42 — Guest checkout flow)
  • Status and priority
  • Epic (if available)
  • Acceptance criteria — the primary input to AI generation

Click a card to expand the full acceptance criteria and reveal the generation actions.

Expanded ticket card showing title, acceptance criteria, and the Generate BDD / Generate Test Cases action buttons

When Jira is your active connector, a Confluence tab appears alongside ticket results. It searches your Confluence space for pages related to the current query — useful for pulling in design specs, business rules, or existing test documentation as additional context for AI generation.

Scrum team filtering​

With the Jira connector, a Scrum Team dropdown filters tickets to a specific team. Filtering runs client-side after fetch. Configure the Jira custom field it reads from in Settings → Integrations → Scrum team field.

Active project​

All generated test cases are saved to the active project, shown in the top bar. Switch projects from the project selector before generating.

What's next​