Jira guide
How tech teams use Jira (without being a developer)
Jira shows up in almost every tech job listing. Here is what it actually is, what the terminology means, and how PMs, QAs, and Scrum Masters use it every day.
What is Jira and why does everyone use it?
Jira is Atlassian's project tracking tool. It was originally built for software bug tracking but has become the default system for sprint planning, backlog management, and project reporting at tech companies of every size.
When a PM says "put it in Jira" or a developer mentions "the ticket," they mean a work item tracked in Jira. When a manager asks about sprint progress, the answer comes from Jira. Non-technical roles — PMs, BAs, QAs, Scrum Masters — spend as much time in Jira as engineers do. Sometimes more.
Key Jira concepts
Six terms you will encounter in your first week.
Issue types
Epic > Story > Task > BugEpics are large bodies of work that span multiple sprints. Stories are user-facing features broken out of an epic. Tasks are technical work items. Bugs are defects. The hierarchy matters — a story always lives under an epic, and bugs are linked to the stories they affect.
Issue status
To Do → In Progress → In Review → DoneEvery ticket moves left to right across the board. 'In Review' means the work is complete and waiting for QA sign-off or a code review before being marked Done. If a ticket goes back from Review to In Progress, the developer picks up the feedback.
Boards
Scrum board vs Kanban boardA Scrum board shows only the tickets committed to the current sprint. Columns are fixed: To Do, In Progress, In Review, Done. A Kanban board shows everything at once — work flows continuously without sprint boundaries. Most product teams use Scrum; support and ops teams often prefer Kanban.
Backlog
The prioritized queue of future workThe backlog is every ticket that exists but has not been pulled into a sprint yet. The PM owns the order — the top of the backlog is what the team works on next. Grooming the backlog means reviewing, clarifying, estimating, and re-ordering tickets regularly.
Sprint
A time-boxed period of focused work (usually 2 weeks)At sprint planning, the team pulls a set of stories from the top of the backlog and commits to completing them within the sprint window. At the end, the team demos what was built (sprint review) and discusses what to improve (retrospective).
Epic
A large body of work containing multiple storiesEpics map to initiatives or features big enough to span multiple sprints. 'User Authentication' might be an epic containing stories for registration, login, forgot password, and social sign-in. Roadmap views in Jira show epics across a timeline.
Jira for Product Managers
PMs live in the backlog. The board tells them what is happening; the roadmap tells them where the team is heading.
- 1
Create and prioritize user stories in the backlog
Write stories in the format 'As a [persona], I want to [action] so that [outcome].' Drag the most important stories to the top of the backlog. Everything above the line becomes a candidate for the next sprint.
- 2
Write acceptance criteria on each ticket
Good acceptance criteria are testable and specific. 'User can log in with email and password and sees their dashboard within 2 seconds.' QA engineers will reference these criteria to write test cases and verify the work is done.
- 3
Use roadmap view to plan quarters
Jira's roadmap view shows epics on a timeline. Use it to communicate what the team is building over the next quarter — to stakeholders, to leadership, and to the team itself. Adjust the timeline as priorities shift.
- 4
Track velocity and sprint progress
Velocity is the average number of story points completed per sprint. Use it to forecast how much work you can plan for future sprints. During a sprint, the board and burn-down chart tell you whether the team is on track to finish.
Jira for QA Engineers
QA engineers are the gatekeepers of the Done column. Their Jira work is about catching problems before they reach users.
- 1
Create bug tickets with the right fields
A useful bug report contains: a short summary, numbered steps to reproduce, the expected behavior, the actual behavior observed, and a severity label (Critical, High, Medium, Low). Incomplete bugs slow down engineers — they have to ask follow-up questions before they can investigate.
- 2
Link bugs to the story they affect
Use the 'Link' field to associate a bug with the story it came from. This gives the PM visibility into which features have open defects and helps the team decide whether to fix a bug before shipping or track it as a known issue.
- 3
Use test management plugins
Zephyr Scale and Xray are the two most common plugins for QA in Jira. Both let you create test cases, link them to stories, record test runs, and track pass/fail results within Jira — without switching to a separate tool.
- 4
Track which bugs are fixed vs open
Filter the board by issue type = Bug to get a dedicated view of open defects. Sort by severity. Before each release, the team reviews this list and decides which bugs are blockers (must fix) and which can ship with known issues documented.
Jira for Scrum Masters
The Scrum Master does not own the backlog or the tickets — they own the process that keeps the team healthy and moving.
- 1
Run sprint ceremonies from the board
Sprint planning starts with the backlog view — the team pulls tickets top-to-bottom until capacity is full. Daily standups use the board — each developer walks their tickets from right to left. Sprint review uses the Done column as the agenda.
- 2
Monitor burn-down charts
The burn-down chart plots remaining work (story points) against time remaining in the sprint. If the line is above the ideal trajectory, the team is behind. The Scrum Master's job is to find out why and remove the blocker — not to pressure the team to move faster.
- 3
Identify and escalate blockers
A blocker is any dependency or impediment that stops a ticket from moving forward. Flag them in standup, add a 'Blocked' label or status in Jira, and start removing them immediately. Unresolved blockers compound — one blocked ticket can stop three others downstream.
- 4
Generate velocity reports
Jira's Velocity Report shows story points completed per sprint over time. Use it in retrospectives to spot trends — a team that delivered 40 points, then 28, then 35 may have had an interruption mid-sprint. Consistent velocity is more valuable than a single high sprint.
How to get Jira experience for free
Jira has a free tier for up to 10 users — no credit card required. Go to atlassian.com/software/jira and create a free account. You get access to Scrum and Kanban boards, the backlog, sprints, and reporting tools.
Create a personal project and add dummy tickets for a fictional product — a mobile app, a website redesign, anything. Practice the workflow end to end: write a user story with acceptance criteria, put it in the backlog, create a sprint, pull the story in, move it across the board, and close the sprint.
Screenshot the board and include it in your portfolio. Employers hiring junior PMs, QAs, and Scrum Masters respond well to candidates who can say "I set up a Jira project and ran three mock sprints" — it shows initiative and removes the question of whether you can find your way around the tool.
Learn the role, not just the tool
Jira fluency matters, but it is table stakes. Hiring managers care whether you know how to run a sprint ceremony, write useful acceptance criteria, or triage a bug backlog. Browse the role tracks to build those skills.
Ready to go deeper?
Build the skills that Jira tracks
Knowing how to use Jira gets you hired. Knowing how to run a sprint, write a testable story, or escalate a blocker gets you promoted. Browse role-specific learning paths — free to start, no coding required.