Skip to content

Common Queries & Reports

Pre-built reports and queries to help you get insights from your test data.

Jira Reports

Report 1: Daily Issue Volume

What it shows: How many new issues your team creates each day, plus resolution trends.

Use it for: - Sprint velocity tracking - Workload management - Identifying bottlenecks

What to look at: - Line chart of issue creation over time - Spike = high activity day (e.g., after release) - Flat line = normal steady state

Report 2: Open Issues by Priority

What it shows: Breakdown of all open issues by priority (High, Medium, Low).

Use it for: - Daily standup - Identifying urgent work - Capacity planning

What to look at: - High-priority count = emergency threshold (e.g., "We have 12 high-priority open bugs") - Pie chart ratio tells you where effort is needed

Query: Filter to Status = "Open" and create a pie chart by Priority

Report 3: Average Resolution Time by Priority

What it shows: How long it typically takes to resolve issues at each priority level.

Use it for: - SLA reporting - Understanding team efficiency - Identifying slow-moving priorities

Example metrics: - High priority: 2 days average - Medium priority: 7 days average - Low priority: 14 days average

Query: Resolve issues, calculate average (Resolved date - Created date), group by Priority

Report 4: Bug vs. Feature Ratio

What it shows: Proportion of bugs vs. features vs. tasks your team is handling.

Use it for: - Technical debt assessment - Roadmap prioritization - Release planning

Example pie chart breakdown: - 40% bugs - 35% features - 25% technical tasks

Query: Pie chart, group by Issue Type, filter to last 30 days

Report 5: Issues by Assignee

What it shows: Distribution of work across team members.

Use it for: - Workload balancing - Identifying over/under-allocated people - Team capacity planning

Example bar chart: - Alice: 15 issues - Bob: 12 issues - Charlie: 8 issues

Query: Bar chart, group by Assignee, sort by count descending

qTest Reports

Report 1: Test Execution Pass Rate

What it shows: Percentage of tests passing vs. failing over time.

Use it for: - Product quality assessment - Regression detection - Release readiness

Example line chart: - January: 92% pass rate - February: 88% pass rate (concerning) - March: 95% pass rate (improving)

Query: Line chart, count test executions, group by date, filter by Status = "Passed" vs. "Failed"

Report 2: Test Cases by Status

What it shows: Breakdown of test cases: Active, Deprecated, In Review, etc.

Use it for: - Understanding test suite health - Identifying stale tests - Planning maintenance

Example pie chart: - 75% Active - 15% In Review - 10% Deprecated

Query: Pie chart, group by Test Case Status

Report 3: Test Coverage by Project

What it shows: How many test cases each project has, relative to code coverage.

Use it for: - Identifying under-tested projects - Allocation of QA resources - Coverage benchmarking

Example bar chart: - Project A: 245 test cases - Project B: 89 test cases - Project C: 156 test cases

Query: Bar chart, count Test Cases, group by Project

Report 4: Defect Aging

What it shows: How long defects remain open, grouped by priority.

Use it for: - SLA tracking - Aging backlog identification - Urgency assessment

Example metrics: - High priority defects: 3 days average age (should be < 1 day) - Medium priority: 10 days average age (should be < 7 days) - Low priority: 30 days average age (acceptable)

Query: Calculate average age (today - creation date), group by Priority

Report 5: Test Execution Frequency

What it shows: How often tests are being executed (daily, weekly, etc.).

Use it for: - Automation health - Release cycle planning - Identifying stale test suites

Example line chart: - Executions per day over last 30 days - Dip on weekends - Spike before release dates

Query: Line chart, count test executions, group by date

Tosca Reports

Report 1: Test Case Count Over Time

What it shows: How many test cases your team has created (growth trend).

Use it for: - Automation coverage growth - Roadmap alignment - Maturity assessment

Example line chart: - January: 500 test cases - March: 750 test cases - May: 1,200 test cases (accelerating)

Query: Line chart, count Test Cases, group by creation date

Report 2: Automation Success Rate

What it shows: Percentage of test executions that pass (vs. fail, skip, blocked).

Use it for: - Test suite stability - CI/CD pipeline health - Release criteria

Example metrics: - 94% pass rate (healthy) - 3% fail rate (needs investigation) - 2% skip rate (technical blockers) - 1% blocked rate (environmental issues)

Query: Pie chart of test execution results, filter to Status = Pass/Fail/Skip/Blocked

Report 3: Test Cases by Type

What it shows: Breakdown of test case types (UI, API, Database, etc.).

Use it for: - Understanding test scope - Identifying gaps (e.g., "no API tests") - Tool planning

Example bar chart: - UI tests: 600 - API tests: 400 - Database tests: 200

Query: Bar chart, count Test Cases, group by Type

Report 4: Execution Trend (Last 30 Days)

What it shows: How often automation runs and average results.

Use it for: - CI/CD pipeline health - Identifying flaky tests (variable pass rates) - Sprint velocity in test automation

Example line chart: - Executions per day: ~25/day - Success rate: 90–95% typically - Dips = failures to investigate

Query: Line chart, count Executions, group by date, avg pass rate

Report 5: Recently Modified Test Cases

What it shows: Test cases that changed in the last 7 days (additions, updates, deletions).

Use it for: - Change control tracking - Impact analysis - Regression scope definition

Example table: | Test Case | Modified | Change Type | Author | |---|---|---|---| | Login_ValidCredentials | 2025-04-18 | Updated | Alice | | Payment_Processing | 2025-04-17 | Added | Bob | | Checkout_Flow | 2025-04-15 | Updated | Charlie |

Query: Table, filter to "Modified Date >= 7 days ago", sort by date descending

How to Create These Reports

  1. Go to your analytiQa dashboard
  2. Select the data source (Jira, qTest, or Tosca)
  3. Set filters (date range, status, project, etc.)
  4. Choose a visualization type (line, bar, pie, table)
  5. Save the report with a name (e.g., "Daily Issue Volume")
  6. Your saved report appears in the sidebar for quick access next time

Sharing Reports

To share a report with teammates:

  1. Open a saved report
  2. Click the Share button (top-right)
  3. Choose sharing method:
  4. Direct link: Send URL (requires login)
  5. Export CSV: Download data, share via email
  6. Embed: Get an embed code for wikis or Slack

Advanced: Building Custom Queries

KQL (Kibana Query Language)

Use the search box to build custom queries. Examples:

Query Finds
status: "Open" All open issues
priority: High AND status: "In Progress" High-priority work being done now
type: Bug AND created: [now-7d TO now] Bugs created in the last 7 days
assignee: "alice@example.com" All items assigned to Alice

Combining Filters

(type: Bug OR type: Task) AND priority: High AND status: "Open"

This finds: All high-priority open bugs and tasks.

Export Options

Click the download icon to export visualizations as:

  • CSV — Open in Excel, pivot tables, custom analysis
  • JSON — Programmatic access, API integration
  • PDF — Email reports, documentation, archiving

Templates by Role

QA Lead / Test Manager

Start with: 1. Test Execution Pass Rate (tracking quality) 2. Test Coverage by Project (identifying gaps) 3. Defect Aging (SLA tracking)

Developer / Scrum Master

Start with: 1. Daily Issue Volume (sprint health) 2. Open Issues by Priority (standup) 3. Average Resolution Time (velocity)

Release Manager

Start with: 1. Bug vs. Feature Ratio (scope control) 2. Automation Success Rate (release readiness) 3. Defect Aging (risk assessment)

Need Help?