Set Up Jira for Software Teams: A Practical 2026 Tutorial

TL;DR: Jira is the default issue tracker for engineering teams for a reason — its Scrum/Kanban projects, backlog, and sprint model map directly onto how software ships. Set it up in six steps: create a Scrum project, configure issue types and a lean workflow, groom the backlog, run sprints on a board, add automations, and connect your repo. Pricing is friendly at the low end: Free for up to 10 users, then $7.91/user/mo (Standard). If your “software team” is really a mixed team that also does docs and ops, ClickUp at $7/user/mo may be the better single workspace. For the full landscape, start with our PM software comparison.

Why Jira for software teams

Jira was built for tracking software work: bugs, stories, epics, releases. Its vocabulary (backlog, sprint, burndown) is the industry standard, so new engineers already know it. If your primary job is shipping code, Jira removes translation overhead that generalist tools impose.

For a single-tool assessment, see the Jira review. If you are weighing Jira against a more general PM tool, the Asana vs ClickUp vs monday comparison is a useful contrast.

2026 Jira pricing

Plan	Price (billed annually)	User limit	What matters for a software team
Free	$0	up to 10 users	Backlog, board, timeline, 100 automation runs/mo, 2 GB storage
Standard	$7.91/user/mo	up to 100,000 users	Rovo AI search, external collaboration, 1,700 automation runs/mo, 250 GB
Premium	$14.54/user/mo	up to 100,000 users	Advanced roadmaps, cross-project dependencies, 24/7 support, 99.9% SLA
Enterprise	Custom	contact sales	Atlassian Analytics, unlimited automation, advanced security

Verified against Atlassian Jira Pricing on 2026-08-28.

Team-perspective tradeoff: If your engineering team is under 10 people, stay on Jira Free — it covers backlog, boards, and sprints with no cost. Move to Standard at $7.91/user/mo only when you need external collaborators (clients/contractors) or more automation runs. Skip Premium ($14.54/user/mo) unless you are coordinating multiple teams with cross-project dependencies and need advanced roadmaps; for a single team it is usually wasted spend. If your team is not purely engineering — you also manage docs, marketing, and client work — ClickUp’s $7 Unlimited plan keeps everything in one workspace instead of bolting Jira onto a second tool.

Step 1 — Create a Scrum project

1. Log in, click Create project → Software → Scrum.
2. Name it after the product or team (e.g., Payments Backend).
3. Choose Team-managed for a self-contained board, or Company-managed if you need shared schemes across multiple teams. Most small teams should pick Team-managed — it is simpler and you will not paint yourself into a permission corner.

Step 2 — Configure issue types and a lean workflow

Default types are Story, Task, Bug, Epic. Keep the workflow short: To Do → In Progress → In Review → Done. Three columns is enough; a five-stage pipeline looks mature but nobody updates the middle three.

• Use Epic only for work spanning multiple sprints.
• Use Bug as a distinct type so it surfaces in filters and reporting.
• Add a Story Points field (Fibonacci: 1/2/3/5/8) for estimation.

Step 3 — Groom the backlog

The backlog is your single source of truth. Rules that keep it healthy:

• Every item has a clear title and a one-line “definition of done.”
• No item larger than one sprint — split epics into stories.
• Prioritize top-down; only the top 10–15 items matter at any time.

A bloated backlog is a graveyard, not a plan. Archive stale items quarterly.

Step 4 — Run sprints on the board

1. Click Create sprint, drag the top backlog items in.
2. Set a fixed length (2 weeks is the default for a reason).
3. During the sprint, move cards across columns. The board is the meeting — standups happen in front of it.
4. At sprint end, close it; unfinished items fall back to the backlog.

Review the Burndown chart after each sprint. If lines consistently flatten near the end, your estimates are off, not your team.

Step 5 — Add automations

Free gives 100 runs/month; Standard gives 1,700. Start with two:

1. When a Bug is created with priority = Highest → assign to on-call and notify.
2. When a story moves to “In Review” → notify the reviewer.

Automation should remove status-chasing, not add process theater.

Step 6 — Integrate your dev tools

Connect your repository (GitHub, GitLab, or Bitbucket) so commits and PRs link to issues automatically. In the project sidebar, go to Project settings → Apps/Integrations, authorize the repo, and prefix branch names with the issue key (e.g., PAY-42). Now every PR shows up on the issue, and “is this merged?” stops being a question.

For advanced cross-team planning, Atlassian’s advanced roadmaps documentation explains dependency modeling on Premium.

Step 7 — Releases and versions

Once stories ship, track them in a Release (team-managed) or Version (company-managed). Attach completed issues to a release, set a release date, and Jira shows what is queued for the next deploy. This connects daily sprint work to the version your customers actually receive — the gap most teams never close. Keep one active release at a time and archive shipped ones so the list stays short.

Step 8 — Read the reports that matter

Jira ships velocity, burndown, and control charts per board. Two you should actually open:

• Velocity — average story points completed per sprint. Use it to plan next sprint capacity, never to judge the team’s worth.
• Control chart — cycle time from “In Progress” to “Done.” A widening band means unpredictability; a tight band means you can promise dates with confidence.

Open these in the sprint retrospective, not in a quarterly review nobody reads.

Permissions and roles (do this early)

Even on a 5-person team, set a Developer role that cannot transition issues to “Done” without review, and a Lead role that can. It takes five minutes in Project settings and prevents the classic “someone marked it done, it wasn’t” incident. Revisit roles when you cross 10 users and hit Jira Free’s ceiling.

Common mistakes

• Company-managed too early. Permission schemes are powerful but a time sink for a 5-person team. Start team-managed.
• A six-column workflow. Nobody updates “Code Review” vs “QA” separately. Keep it to four.
• Skipping sprint length discipline. Sprints that silently extend to three weeks defeat the purpose.
• Paying for Premium prematurely. Advanced roadmaps are great at scale, useless for one team.

Best for whom

Jira is the right call for engineering-led teams shipping software, especially once you pass 10 users and need structured backlog, sprint, and release tracking. It is the wrong call for a generalist team that also does content, ops, and client work — there, a single all-in-one tool like ClickUp avoids running two systems. Start free, earn your way to Standard, and only reach for Premium when cross-team dependency planning becomes a real bottleneck.

---

Pricing verified against Atlassian Jira Pricing on 2026-08-28.