Jira Power User Training for SQA

Navigate from a Jira project to the Issue Navigator and locate relevant issue details.

Construct basic searches with Jira’s available field-based search controls.

Configure Issue Navigator columns to create an SQA review view.

Sort search results to prioritize issues by risk, age, priority, or target release.

Save, update, copy, and manage a reusable filter without administrator access.

Share or subscribe to a filter while respecting Jira permissions.

Export a controlled set of search results for offline review or audit evidence.

Identify the fields, operators, values, keywords, and functions in a JQL clause.

Write JQL queries for project, issue type, status, resolution, priority, component, and version.

Combine JQL clauses correctly with AND, OR, NOT, and parentheses.

Use text, label, assignee, reporter, and current-user criteria in JQL queries.

Use ORDER BY with multiple fields to produce review-ready result sets.

Translate a plain-language SQA question into a valid JQL query.

Diagnose and correct common JQL syntax, field, value, and permission errors.

Use absolute and relative dates in JQL to define repeatable monitoring windows.

Query empty and populated fields correctly with EMPTY, NULL, and IS operators.

Use Jira date functions to create filters that remain current over time.

Use status-history operators such as WAS and CHANGED to examine workflow behavior.

Construct JQL that identifies unresolved defects older than a defined threshold.

Construct JQL that identifies potentially stalled work from status and update history.

Construct JQL that highlights testing delays or release slippage using workflow dates, due dates, and versions.

Explain how a Jira Software board uses a saved filter to determine its issue scope.

Distinguish a Kanban board’s backlog, active workflow view, and completed work.

Evaluate how board columns map workflow statuses into process stages.

Create Quick Filters for common SQA monitoring views.

Configure or interpret swimlanes that expose priority, ownership, or classes of service.

Interpret Work in Progress limits as signals of flow risk rather than productivity targets.

Use a Kanban board to locate queues, blocked work, excessive WIP, and bottlenecks.

Distinguish Scrum and Kanban board behavior and select the appropriate view for an SQA question.

Interpret sprint, backlog, and incomplete-work information without treating Jira as proof of process compliance.

Trace an issue through workflow statuses and transitions using its history.

Identify workflow-control weaknesses such as skipped stages, invalid resolutions, and repeated reopening.

Use versions, fix versions, and release status to assess release scope and readiness.

Use issue links to represent and inspect dependencies, blockers, and related work.

Trace a sample item across Epic, Story or Task, Bug, dependency, and release records.

Create a personal Jira dashboard and configure its layout and access permissions.

Configure filter-based gadgets to monitor workload, ownership, status, priority, and release exposure.

Interpret the Created vs Resolved report as a trend in incoming and completed work.

Interpret Average Age while accounting for unresolved-issue scope and outliers.

Interpret a Cumulative Flow Diagram to identify growing queues, excessive WIP, and flow instability.

Interpret a Control Chart to assess cycle-time variation and investigate unusual items.

Build an SQA dashboard that combines complementary indicators without presenting misleading conclusions.

Define a Jira-based audit scope, review period, criteria, and sampling approach.

Assess whether Jira data is sufficiently complete and consistent to support an audit conclusion.

Use filters and issue history to test adherence to workflow and closure controls.

Analyze ageing issues, unresolved defects, stalled work, bottlenecks, testing delays, and release slippage.

Collect reproducible Jira evidence while recording query scope, date, and relevant limitations.

Classify observations as conforming evidence, exceptions, risks, or items requiring further investigation.

Perform a final SQA process audit and communicate evidence-based findings, limitations, and corrective-action follow-up.