Jira for Testers

Jira is the most widely used tool for defect tracking and Agile project management, and testers use it every day: logging bugs, following sprint work, filtering what needs retesting and reporting quality to the team. This guide covers Jira from a tester's point of view — the concepts, a bug report template, the defect life cycle, the JQL queries QA engineers actually use, and how test management fits in.

Advertisement

Why Testers Use Jira

  • Defect tracking — every bug has an owner, a status and a history.
  • Sprint visibility — see which stories are ready for testing and which bugs block a release.
  • Traceability — link stories, test cases, bugs and code changes together.
  • Reporting — filters and dashboards show open bugs, reopen rates and release readiness.
  • Collaboration — comments, mentions and watchers keep developers, testers and product owners aligned.

Core Jira Concepts

Concept What it means for a tester
Project A container for one product or team's work, with a key like SHOP (issues become SHOP-101, SHOP-102…).
Issue Any unit of work — a story, task or bug.
Epic A large feature broken into stories, e.g. "Checkout redesign".
Story A user-facing requirement you test against its acceptance criteria.
Task / Sub-task Technical or smaller pieces of work, e.g. "Write regression tests for checkout".
Bug A defect — the issue type testers create most.
Workflow & status The path an issue follows (e.g. To Do → In Progress → In Review → Done) and where it is now.
Board A visual view of issues in columns — Scrum boards for sprints, Kanban boards for continuous flow.
Backlog & sprint The prioritized list of work, and the time-boxed slice of it the team commits to.
Component, label, fix version Ways to group issues — by module, by tag, and by the release they'll ship in.

Details: Jira Fundamentals and Fields, Links & Actions.

A Tester's Day in a Jira Sprint

  1. Check the board for stories moved to Ready for QA (or your team's equivalent).
  2. Test each story against its acceptance criteria; comment with results.
  3. Log bugs for failures and link them to the story.
  4. Retest bugs marked fixed; close them or reopen with evidence.
  5. Run your saved filters to see what's pending, and update the sprint's QA status before stand-up.

More on ceremonies and boards: Boards, Sprints & Agile in Jira and Agile Scrum for Testers.

How to Write a Good Bug Report in Jira

A bug that a developer can reproduce in two minutes gets fixed. A vague one bounces back as "Cannot Reproduce". Use a structure like this:

Field Example
Summary Checkout: "Place order" button stays disabled after applying a valid coupon
Environment QA · build 2.4.0-rc2 · Chrome 131 · Windows 11
Preconditions Logged in as a customer with 2 items in the cart
Steps to reproduce 1. Go to Checkout 2. Enter coupon SAVE10 3. Click Apply
Expected result Discount applied and "Place order" enabled
Actual result Discount applied but "Place order" remains disabled
Severity / Priority High / High — customers can't complete purchases with coupons
Attachments Screenshot, short screen recording, console/network log
Links "Relates to" the story SHOP-214; affects version 2.4.0; component Checkout

Write the summary so it makes sense on its own in a list: where + what's wrong. More in Working With Jira Issues.

The Defect Life Cycle in Jira

A common bug workflow looks like this, though every company customizes it:

New → Open → In Progress → Fixed → Ready for Retest → Closed, with Reopened when a retest fails.

When a bug is closed, the resolution field records why: Fixed/Done, Won't Fix, Duplicate, Cannot Reproduce, or Works as Designed. Watching resolutions matters — lots of "Cannot Reproduce" usually means bug reports need better steps or environment details.

Full detail: Defect Bug Management.

Severity vs Priority

Severity is the impact on the system; priority is how urgently the business wants it fixed. They're set by different people for different reasons, so all four combinations occur:

  • High severity, high priority — payment fails for all users.

  • High severity, low priority — a crash in a rarely used legacy report.

  • Low severity, high priority — the company logo is wrong on the home page.

  • Low severity, low priority — a typo in the FAQ page footer.

See Severity vs Priority.

JQL: 10 Queries Every Tester Uses

JQL (Jira Query Language) lets you filter issues precisely and save the results as filters for boards and dashboards. Replace SHOP with your project key:

-- 1. All open bugs in the project
project = SHOP AND issuetype = Bug AND resolution = Unresolved

-- 2. Bugs assigned to me, most urgent first
issuetype = Bug AND assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC

-- 3. Bugs I reported in the last 7 days
issuetype = Bug AND reporter = currentUser() AND created >= -7d

-- 4. Bugs in the current sprint
project = SHOP AND issuetype = Bug AND sprint in openSprints()

-- 5. Ready for retest (use your workflow's status name)
project = SHOP AND issuetype = Bug AND status = "Ready for Retest"

-- 6. Critical and high-priority bugs still open
project = SHOP AND issuetype = Bug AND priority in (Highest, High) AND resolution = Unresolved

-- 7. Bugs targeted for a release
project = SHOP AND issuetype = Bug AND fixVersion = "2.4.0"

-- 8. Bugs reopened this week
project = SHOP AND issuetype = Bug AND status CHANGED TO "Reopened" DURING (startOfWeek(), now())

-- 9. Stale bugs nobody has touched in two weeks
project = SHOP AND issuetype = Bug AND resolution = Unresolved AND updated <= -14d

-- 10. Search the text of issues
project = SHOP AND issuetype = Bug AND text ~ "checkout timeout"

Keep more in the Jira & JQL Cheat Sheet, and learn filters in Search, Filters, JQL & Dashboards.

A QA Dashboard That Actually Helps

Build a dashboard from saved filters with a few gadgets:

  • Filter Results — your "ready for retest" and "open critical bugs" lists.
  • Two-Dimensional Filter Statistics — open bugs by component and priority, to spot problem areas.
  • Created vs Resolved Chart — are bugs being fixed as fast as they're found?
  • Pie Chart — bugs by status or by assignee for the current release.

Test Management in Jira

Jira doesn't include test cases out of the box. Teams add a test management app — commonly Xray or Zephyr — which adds test cases, test cycles/executions and coverage reports inside Jira. The key benefit is traceability: story → test cases → executions → bugs, so you can answer "is this story fully tested?" in one view.

Learn more: Test Management in Jira: Zephyr & Xray.

Integrations for Automation Testers

  • Git — include the issue key in branch names and commit messages (SHOP-214 fix coupon validation) and Jira shows the development activity on the issue.
  • Jenkins / CI — link builds and deployments to issues so you know which build contains a fix before you retest.
  • Automation results — test frameworks can push results to Xray/Zephyr, or create bugs through Jira's REST API.
  • Confluence — test plans and strategies linked to epics.

See Jira Integrations and Jira Administration.

The Learning Path

Part 1 — Core Jira

Part 2 — Search & Test Management

Part 3 — Integration & Admin

Part 4 — Interview Readiness

How to Use This Guide

  • Beginners: read this page, then Parts 1 → 4 in order.
  • Daily use: bug reports, boards and sprints, and the 10 JQL queries above.
  • Interview prep: defect life cycle, severity vs priority, JQL, and the scenario-based questions.

From Real Projects

I've used Jira for test execution follow-up and defect tracking on every project — Apkope, Canolog and Testsigma — alongside TestRail for tracking test case execution. My day-to-day work included preparing bug reports, following each defect through its life cycle, and retesting fixes. On Testsigma I was also involved in verifying customer tickets, which taught me to write reports that anyone — developer, support or product — can reproduce without asking questions: clear steps, expected versus actual, and evidence attached.

📖 Related tutorials

📚 Official documentation: Jira Cloud documentation (Atlassian) · ISTQB Glossary of testing terms

Frequently Asked Questions

Why do software testers use Jira?

For defect tracking, following sprint work, test execution tracking (with Xray or Zephyr), traceability between stories and bugs, and reporting quality through filters and dashboards.

What is JQL?

Jira Query Language — a search language for filtering issues by fields such as project, issue type, status, assignee, sprint, priority, labels and dates. Saved JQL filters power boards, dashboards and subscriptions.

What is the defect life cycle in Jira?

The stages a bug moves through, commonly New → Open → In Progress → Fixed → Ready for Retest → Closed, with Reopened when a retest fails. The exact workflow depends on your company's Jira configuration.

What is the difference between severity and priority?

Severity is the defect's impact on the system; priority is how urgently the business wants it fixed. A defect can have any combination of the two.

Can Jira manage test cases?

Not by default. Teams add a test management app such as Xray or Zephyr to create test cases, run test cycles and link executions to stories and bugs.

What makes a good bug report?

A clear summary, the environment and build, precise steps, expected vs actual results, severity and priority, evidence (screenshots, logs, recordings) and links to the related story. See also: Project Interview Questions for Testers.

How does Jira integrate with automation frameworks?

Through Git and CI integrations (linking commits, builds and deployments to issues), test management apps that import automated results, and Jira's REST API for creating or updating issues automatically.

What is the difference between a Scrum board and a Kanban board?

A Scrum board works in time-boxed sprints planned from a backlog. A Kanban board shows a continuous flow of work, often with limits on how many items can be in each column.

Keep Learning