Skip to main content
Version: 1.0.7

Issue Tracker

Issue Tracker connects defects to Test Plans, Test Runs, and optional execution results. It supports native RabbitQA issues and connected Jira or Azure views according to organization configuration.

Read and filter issues​

The summary cards show Resolved / Total Issues, To Do, Top Priority, and In Progress. Search by issue key, summary, or description, then filter by Plan, Test Run, Status, and Priority.

Issue summary, filters, search, and Table view

More Filters adds Labels, Assignee, and Date Range. Export Excel exports the current issue list. Filters and board selection do not change issue state.

Table and board views​

ViewSource
TableThe currently filtered issue list.
RabbitQA BoardNative RabbitQA issues grouped by workflow status.
Jira BoardJira issues available through the configured Jira connection.
Azure BoardAzure DevOps work items available through the configured connection.

RabbitQA native issue board

An empty external board does not prove that the connection is broken; it can also mean that no matching issues exist for the selected scope.

Create an issue​

Select New Issue. The first required field is labeled Project, but it supplies the Test Plan context.

Required Test Plan context for a new issue

  1. Select the Test Plan.
  2. Optionally select a Test Run.
  3. Optionally link an execution result.
  4. Select Continue.
  5. Enter Summary and Description.
  6. Set Labels, Priority, and Status.
  7. Add attachments when needed.
  8. Select Create Issue, or use an offered external send action when that integration is configured.

New issue scoped to a Test Plan, Test Run, and execution

Use Link Issue when an external issue connection and matching records are available. The action can be unavailable when no supported connection is configured or the role lacks permission.

Execution boundary​

An issue can be created from Test Execution, but issue creation does not save a draft execution result. Return to the execution and select Save Result if the result itself must persist.

Correct use​

  • Select the correct plan and run before creating or interpreting an issue.
  • Include observed behavior and evidence; do not copy unsupported assumptions into a defect.
  • Use RabbitQA Board for native issues and the named external board for connected records.
  • Verify the result link when traceability to a specific execution is required.