Key takeaways
- A bug tracker is the team's shared record of work: stories, tasks and bugs, each with an owner and a status. Jira is the most common; Azure DevOps, GitHub Issues, Linear and YouTrack work the same way.
- As a tester you'll mostly create bugs, link them to stories, follow them through the workflow and search with filters. Learn a few JQL queries and you'll save hours.
- Test cases often live in an add-on (Xray, Zephyr) or a separate tool (TestRail), linked to the same stories and bugs.
What a tracker is for
A team might handle hundreds of pieces of work at once. The tracker answers: what needs doing, who's doing it, and what state is it in?
For testers, it's where your work becomes visible. A well-written bug in the tracker is your main output; a vague one wastes everyone's time.
Issue types
Jira calls every item an issue. The common types:
| Type | What it is | Example |
|---|---|---|
| Epic | A large feature, split into stories | "Saved payment cards" |
| Story | A piece of user value, from the user's view | "As a customer, I want to save my card during checkout" |
| Task | Work that isn't a user feature | "Set up a test environment for payments" |
| Bug | Something that doesn't work as it should | "Saved card disappears after logout" |
| Sub-task | A smaller step inside a story or task | "Test saved cards on Safari" |
The fields you'll fill in for a bug
| Field | What to put in it |
|---|---|
| Summary | One line: what's wrong, where, under what condition. "Checkout: saved card not shown after re-login" |
| Description | Steps to reproduce, expected result, actual result, environment. See how to write a great bug report. |
| Priority | Your suggestion; the team may change it. See severity vs priority. |
| Severity | If your project has this field: the impact. |
| Affects version / Environment | The build and where you found it: "4.2.0, staging, Chrome 130" |
| Component / Labels | The area of the product, so the right team sees it |
| Attachments | Screenshots, a short video, logs, the failing request from DevTools |
| Links | "relates to" the story; "duplicates" another bug; "blocks" a release |
Workflows and boards
Every issue moves through a workflow of statuses, such as To Do → In Progress → In Review → In QA → Done. Bugs follow the bug life cycle. Each team configures its own, so ask to see yours.
A board shows issues as cards in columns, one column per status:
- Scrum boards show the current sprint.
- Kanban boards show a continuous flow.
As a tester, you'll watch the "In QA" or "Ready for test" column: that's your queue.
Searching with JQL
Jira's search language, JQL (Jira Query Language), lets you build lists you'll check every day. A few useful examples:
-- Bugs I reported that are still open
reporter = currentUser() AND type = Bug AND statusCategory != Done
-- Everything waiting for me to test
status = "Ready for QA" AND assignee = currentUser()
-- New critical bugs in the last 7 days
type = Bug AND priority in (Highest, High) AND created >= -7d
-- Open bugs in the payments area, newest first
project = SHOP AND component = Payments AND type = Bug
AND statusCategory != Done ORDER BY created DESC
Save the useful ones as filters, and add them to a dashboard.
Where test cases live
Jira itself doesn't manage test cases. Teams usually use one of these:
- Xray or Zephyr: Jira add-ons where test cases are Jira issues, linked to stories, with test runs and results.
- TestRail, qTest and similar: separate tools that integrate with Jira.
- Azure Test Plans, if the team uses Azure DevOps.
- Sometimes just a spreadsheet or Confluence page, in small teams.
The value is the links: story ↔ test cases ↔ runs ↔ bugs. That's how you get a traceability view.
How to practise before your first job
Atlassian offers a free Jira plan for small teams. Create a project, then:
- Create an epic and three stories for a website you use, with acceptance criteria.
- Test the real website and log five real (or realistic) bugs with full details.
- Link each bug to its story, and move them through a workflow.
- Write three JQL filters and put them on a dashboard.
Screenshots of this make a good addition to a portfolio.
A team's tracker had over 200 open bugs. Many had summaries like "Error", "Doesn't work" or "Problem on page". Nobody could tell which were duplicates, which were fixed, or which mattered.
A new tester proposed three simple rules: every bug summary names the area, the action and the symptom; every bug has a component; and every bug is linked to a story or epic. The team spent one afternoon cleaning up. About forty bugs turned out to be duplicates or already fixed, and were closed.
Triage meetings went from an hour to twenty minutes, because the team could filter by component and see what was new.
Lesson: a tracker is only as useful as what's written in it. Clear summaries, components and links are what make bugs findable.
Do
Summary: "Checkout – saved card missing after logout and login (Chrome, staging 4.2.0)". Linked to story SHOP-231, component Payments, video attached.
Don't
Summary: "Card bug". No component, no link, no version, so it's invisible to filters and hard to triage.
Check yourself
You find a bug while testing a story. Should you create a separate Bug issue, or just comment on the story? What's a sensible rule?
Show answer
A common rule: if the bug is found while the story is still in progress in the current sprint and will be fixed before the story is done, many teams just comment or create a sub-task, so the story can't be closed with it open. If the bug is in already released functionality, or won't be fixed right away, create a separate Bug and link it to the story. Ask what your team's convention is; the point is that no bug gets lost.
