How to Use Jira: The Beginner's Guide (First Project, First Sprint, and a Board That Stays Honest)

CodexFuse Team · 2026-10-28T14:28:09.225Z · 21 min read

Jira turns scattered tasks into a board everyone can read. This beginner's guide walks you through your first project, your first sprint, and the habits that keep the board honest.

Learning how to use Jira takes about an hour of real practice, and it pays off every week after that. Jira is Atlassian's project management tool for planning, organizing, and tracking work, and it is the board most software teams live in — but marketing, operations, and HR teams use it too. If you just joined a team that runs on Jira, this guide takes you from a blank account to your first finished sprint: create a project, pick the right template, write issues people can actually finish, run a sprint, and read the reports that tell you whether the board is honest.

The short version: you create a space for your team, pick a template that matches how you work, add work items to a backlog, drag them across a board, and check the burndown chart to see if you will finish on time. Everything else in Jira is a refinement of that loop. If you already use a simpler board, our Trello beginner guide covers the lightweight end of the same idea — Jira is what you graduate to when a team needs sprints, issue types, and reports.

What is Jira?

Jira is a project management and issue-tracking tool from Atlassian that teams use to plan work, assign it to people, track its progress on a board, and report on what got done. It started as a tool for software teams practicing agile methods like Scrum and Kanban, and it has grown into a general work tracker used by product, marketing, operations, and support teams. The name comes from "Gojira," the Japanese word for Godzilla, according to Guru99's long-running Jira tutorial.

Three ideas explain almost everything in Jira. A space (called a project in older Jira versions) holds all the work for one team, along with its board, backlog, and settings. A work item — Jira's current name for what used to be called an issue — is one unit of work: a story, a task, a bug, or an epic. And a board is the visual view of that work, arranged in columns that match your workflow, usually To Do, In Progress, and Done. Atlassian's own getting-started guide puts it even more simply: create a space, pick a template, set up your columns, add your first work item, invite your team, and start moving work through the workflow.

How do I create my first Jira project?

Creating your first Jira project takes about ten minutes, and the setup follows the same seven steps Atlassian documents in its getting-started guide. You do not need to know Scrum or Kanban first — the templates come pre-configured, and you adjust them as you go.

1. Sign up and name your site. Create a free Atlassian account and pick a site name, which becomes your address in the form your-company.atlassian.net. The Free plan covers up to 10 users, so a small team can start without paying anything.
2. Create a space. Log in to your Jira site, select the plus icon in the sidebar, and create a space for your team or project. A space holds the board, the backlog, and the settings for that piece of work.
3. Pick a template. Choose the template closest to how your team already works: Scrum for teams that plan in sprints, Kanban for continuous flow, or bug tracking for a simple list view. You can change most settings later, so do not overthink this choice.
4. Choose team-managed or company-managed. For the Scrum and Kanban templates you also pick a space type. Team-managed spaces are set up and maintained by the team itself and suit independent teams. Company-managed spaces are set up by Jira admins and share workflows across many teams, which suits larger organizations that need one standard way of working.
5. Set up your columns. Your board shows work items in columns, and each column is one stage of your workflow. Start with the columns that match how your team already works — usually To Do, In Progress, and Done — and add a Review column only if someone actually reviews work before it counts as done.
6. Create your first work item. Select + Create in the top navigation bar, or press C on your keyboard. Give it a summary, a type, and an assignee, and it lands in your backlog — or directly on the board if your space has no separate backlog.
7. Invite your team. Once a few work items are on the board, invite your teammates so they can see the work, pick up tasks, and collaborate in the same place. If your team coordinates in chat, our Microsoft Teams beginner guide covers the other half of that setup.

That is the whole first setup. If you get stuck on any step, the template defaults are a safe place to stay for your first sprint — you will learn more from one real sprint than from a week of configuring settings.

Scrum or Kanban: which template should I pick?

Pick Scrum if your team works in fixed-length sprints with a planning meeting and a regular delivery cadence, and pick Kanban if work arrives continuously and you ship it as soon as it is ready. The two templates differ in exactly one structural way: Scrum adds a backlog, sprint planning, and a time box; Kanban skips the time box and manages flow instead.

Beginners often ask whether they need to understand agile theory before choosing. Atlassian's answer is no: the Scrum and Kanban templates come pre-configured, so you start with the one that best matches how your team works and adjust as you go. If you genuinely cannot decide, pick Kanban — it has fewer moving parts, and you can switch to Scrum later once the team has a rhythm. The bug-tracking template is the third option: a simple column-based board for teams that mainly need to log and fix defects.

What is an issue in Jira?

An issue — now called a work item in the current Jira interface — is any single unit of work: a task, a bug, a user story, or an epic. The word confuses beginners because "issue" sounds like a problem, but in Jira it just means "a thing someone has to do." Every work item has the same anatomy: a summary, a type, a status, an assignee, a priority, and a description, with comments and attachments alongside.

The hierarchy matters because it is how Jira rolls work up: sub-tasks sit inside stories and tasks, stories sit inside epics, and the epic is what a manager reports on. A common beginner mistake is creating everything as a task and losing the picture; grouping stories under one epic is what turns a pile of cards into a plan. To create one, click Create in the top navigation, choose the type, fill in the summary and description, set the priority and assignee, and click Create — the item lands in your backlog, ready to be prioritized.

How do I write an issue people can actually finish?

An issue people can actually finish has a summary that states the outcome, a description that states the acceptance criteria, and a size small enough to complete inside one sprint. Write the summary as a verb phrase — "Add password reset email" beats "Password stuff" — and write the description so that any teammate could pick it up cold: what needs to change, how you will know it works, and what is out of scope.

Keep issues small and clear. A story that takes more than half a sprint is a sign it should be split; the split usually falls along obvious lines, such as one story per screen, per user role, or per integration step. Add labels and components to categorize work so filtering is fast later — "mobile," "checkout," and "billing" as labels will save you more time than any workflow customization in your first month. And set the priority honestly: if everything is High, nothing is, and the board stops telling the truth about what matters most.

How do I build a backlog that actually works?

A backlog that works is a ranked list, not a storage drawer: the most important item sits at the top, and everything below it is ordered by what the team should do next. Jira's backlog is where you create and prioritize issues before they enter a sprint, and the discipline is in the ordering — prioritize ruthlessly and keep the most important items at the top.

Groom the backlog once a week, even if the session is only fifteen minutes. Delete duplicates, close items that no longer matter, split anything too big for a sprint, and re-rank the top ten so the next sprint planning starts from a clean list. A backlog with two hundred stale items is worse than a backlog with twenty live ones, because nobody trusts a list that is mostly dead. The refinement habit is also where estimation happens: the team assigns story points — a relative measure of effort, not hours — so that sprint planning becomes a capacity question instead of a guessing game.

How do I run my first sprint?

You run your first sprint by pulling a realistic set of issues from the backlog into a sprint, starting it, working the board for one or two weeks, and then reviewing what finished. Pick a two-week sprint for your first one: one week is too short to learn the rhythm, and three weeks is long enough for the plan to go stale.

1. Open the backlog and create a sprint. In your project's sidebar, select Backlog, then click Create Sprint. A new sprint section appears at the top of the backlog.
2. Drag issues into it. Move issues from the backlog into the sprint until the total story points match what your team has finished in a typical week, doubled. For a first sprint, deliberately under-commit — finishing early teaches the team more than over-committing and missing.
3. Name it and set the dates. Call it Sprint 1 and set a start and end date. Two weeks, Monday to Friday, is the standard first choice.
4. Click Start Sprint. The sprint moves to the board view, and the clock starts. From here, work moves across the columns as it progresses.
5. Work the board daily. Each person drags their own items from To Do to In Progress to Done, and the team meets briefly each day to say what moved, what is blocked, and what needs help.
6. Close it and review. At the end date, complete the sprint. Unfinished issues move to the next sprint or back to the backlog — never extend the sprint deadline, because the time box is what makes the next plan honest. Then hold a short retrospective: what went well, what did not, and one change for next time.

Here is what a realistic first sprint looks like for a small team building a website feature. The project key is WEB, the sprint is two weeks (10 working days), and the team commits to 34 story points — a deliberately modest load for a first attempt.

The math is the point: 8 + 8 + 5 + 3 + 3 + 3 + 2 + 2 equals 34 points across 10 working days, so the ideal burn rate is 3.4 points per day. If the burndown chart shows 17 points remaining at the end of day five, the sprint is exactly on track; if it shows 28, the team is behind and should cut scope rather than work longer hours. That single checkpoint is the most useful number in Jira for a beginner.

How do I use the board day to day?

Day to day, the board is a three-step habit: pick the top item in your column, move it when its state changes, and leave a comment when it gets stuck. Drag an issue across columns as work progresses — To Do, In Progress, Done — and update the status yourself rather than waiting for someone else to do it, because a board that nobody updates stops reflecting reality within a day.

Two habits keep the board honest. First, limit work in progress: if the In Progress column holds more items than people, nothing finishes, because everyone is half-started on three things. Kanban teams set explicit WIP limits per column; Scrum teams get the same effect from the sprint commitment. Second, keep the daily check-in short and board-driven: stand in front of the board, look at what moved since yesterday, and talk only about blocked items. Status meetings that re-read every card waste the one thing the board was built to save — time.

Connect the tools your team already uses, and the board updates itself. Jira connects to GitHub, Slack, Figma, and Confluence through Marketplace apps, so a pull request or a comment in Slack can show up alongside the work item it belongs to. If your code lives in GitHub, our GitHub beginner guide covers the repository side of that connection.

How do I read Jira's reports?

Jira's reports answer two questions: are we on track this sprint, and how much can we take on next sprint. You only need two reports as a beginner, and both live under Reports in the project sidebar.

Take the sprint example above: 34 points over 10 working days gives an ideal line of 34, 27, 24, 20, 17, 14, 10, 7, 3, and 0 points remaining from day zero through day ten (3.4 points per day, rounded). Compare your actual remaining work against that line each morning. If the actual line sits above the ideal line for three days running, the sprint is at risk and the honest move is to move an issue back to the backlog, not to quietly extend the deadline. Velocity works the same way over time: if your last three sprints finished 30, 34, and 28 points, plan the next one at about 31 — the average — and treat the 34 as a good week, not a new normal.

Dashboards pull these reports together for the whole team. Create one from the Dashboards menu at the top of Jira and add gadgets such as Sprint Health, a pie chart of issues by status, and the burndown chart, so the project's health is visible at a glance without opening each report separately.

How much does Jira cost in 2026?

Jira Cloud is free for up to 10 users, and paid plans start at $8.48 per user per month. The prices below come from Atlassian's own pricing page, checked on October 28, 2026 — re-check before you budget, because Atlassian changes list prices and the figures shown are the monthly-billing rates.

Three cost details matter more than the headline prices. First, the Free plan is genuinely free forever for up to 10 users with 2 GB of storage — but if you add an 11th user, Atlassian automatically starts a 7-day free trial of the Standard plan, so the free tier ends exactly when your team grows past ten. Second, automation is metered: the Free plan allows 150 automation steps per subscription per month, Standard allows 400 per user per month, and Premium allows 750. Third, Jira's AI assistant, Rovo, is included only on paid plans — 25 credits per user per month on Standard, 70 on Premium, and 150 on Enterprise — and the Free plan does not include it at all. Rovo can break work into tasks, draft descriptions, and build workflows from plain-language descriptions, but it is a paid-plan feature, not a free one.

What is Jira automation, and which rules should I set first?

Jira automation runs small if-this-then-that rules on your work items, so the board updates itself instead of waiting for someone to remember. A rule has a trigger, a condition, and an action: when an issue moves to Done, for example, automation can assign its sub-tasks, notify the reviewer, or move the parent story along. The Free plan's 150 steps per month is enough for a small team's first rules, and Standard's 400 per user per month covers most growing teams.

Set these three rules first, in this order. When an issue is created without an assignee, assign it to the project lead so nothing sits unowned. When a sub-task is marked done, comment on the parent story with the update, so the story's history stays complete. And when an issue moves to Done, automatically move its linked pull request reviewer into the loop — or, simpler still, send a Slack message to the team channel. One honest warning: automation that nobody understands becomes invisible process debt, so write the rule's purpose in its name — "Assign unowned issues to lead," not "Rule 1."

Jira vs Trello: which one should I use?

Use Jira when your team needs sprints, issue types, and reports, and use Trello when you need a simple shared board with almost no setup. They are both Atlassian products, and they solve the same problem at different scales: Trello is a board, Jira is a board plus a planning system.

The practical rule: if your team holds sprint planning meetings, you need Jira; if your team just needs to see who is doing what, Trello is enough and faster. Many teams use both — Trello for a lightweight roadmap or content calendar, Jira for the engineering work. Our Trello beginner guide walks through the simple end in the same step-by-step style as this guide.

7 mistakes beginners make in Jira

Most Jira frustration comes from seven avoidable mistakes, and fixing them takes an afternoon. Work through this list after your first sprint, not before — the mistakes only make sense once you have felt them.

1. Creating issues the size of epics. If a story cannot finish inside one sprint, split it. Big issues hide risk and make the burndown chart lie.
2. Skipping the backlog and planning straight onto the board. Unranked work becomes whoever-shouts-loudest work. Groom the backlog weekly.
3. Over-committing the first sprint. Plan the first sprint at half of what you think the team can do. Finishing early builds trust; missing by a mile builds cynicism.
4. Adding columns for every status. A board with nine columns is a flowchart, not a board. Three or four columns, plus Review if you truly review, is enough.
5. Marking everything High priority. Priority is a ranking, not a feeling. If everything is High, the board cannot tell the team what to do first.
6. Extending the sprint instead of cutting scope. The time box is the discipline. Move unfinished work to the next sprint and let velocity tell the truth.
7. Configuring before doing. Custom workflows, fields, and schemes feel productive and teach nothing. Run two sprints on the defaults, then customize only what hurt.

Sources

Atlassian, "How to Use Jira: An Introduction" — the seven-step first setup (create a space, pick a template, set up columns, create a work item, connect tools, invite the team, move work forward), team-managed vs company-managed spaces, and Rovo AI on paid Cloud plans only; updated September 15, 2026. atlassian.com/software/jira/guides/getting-started/basics

Atlassian, "Jira pricing" — Free $0 for up to 10 users with 2 GB storage, Standard $8.48 per user per month with 250 GB, Premium $15.56 per user per month with unlimited storage and a 99.9% uptime SLA, Rovo credits (25 Standard / 70 Premium / 150 Enterprise per user per month), automation step limits, and the 7-day Standard/Premium trial; checked October 28, 2026. atlassian.com/software/jira/pricing

Everhour, "How to Use Jira in 2026: A Beginner's Guide to Project Success" — account and site-name setup, template choice, interface tour (sidebar, backlog, board, reports), sprint creation steps, burndown and velocity charts, WIP limits, and story points vs time estimates; updated September 11, 2026. everhour.com/blog/how-to-use-jira

Guru99, "JIRA Tutorial for Beginners" — what Jira is used for (bug tracking, issue tracking, project management), the Gojira name origin, the six-step beginner setup, and the teams Jira helps; updated about 19 days before October 28, 2026. guru99.com/jira-tutorial-a-complete-guide-for-beginners

ones.com, "Jira Project Management Tutorial for Beginners" — issue creation and management steps, workflow and board customization, and the definition of an issue as a task, bug, or user story; updated about 70 days before October 28, 2026. ones.com/blog/jira-project-management-tutorial-beginners

Trello, "Which Trello Plan Is Best for You?" — Free plan $0 for up to 10 collaborators per workspace, Standard $5 per user per month billed annually; checked October 28, 2026. trello.com/pricing

Frequently Asked Questions

Is Jira free?

Yes, for small teams. Jira Cloud's Free plan costs $0 for up to 10 users with 2 GB of storage and community support. If you add an 11th user, Atlassian automatically starts a 7-day free trial of the Standard plan ($8.48 per user per month). The Free plan does not include Rovo AI — that starts on the paid plans.

Do I need to know Scrum or Kanban before I start using Jira?

No. Atlassian's own getting-started guide says the Scrum and Kanban templates come pre-configured, so you start with the one that best matches how your team works and adjust as you go. You will learn the method faster from running one real sprint than from reading about it first.

What is the difference between a Jira issue and a task?

An issue — now called a work item — is the umbrella term for any unit of work in Jira, while a task is one specific issue type. The other types are epic, story, sub-task, and bug. If someone says "create an issue," they mean create a work item of whichever type fits.

Should my team use Scrum or Kanban in Jira?

Use Scrum if your team plans work in fixed one- or two-week sprints and commits to a sprint goal. Use Kanban if work arrives continuously and you ship each item as soon as it is ready. If you cannot decide, start with Kanban — it has fewer moving parts, and you can switch to Scrum later.

Is Jira only for software developers?

No. Jira started with software teams, but marketing, HR, operations, and support teams now use it to track their own work. Any team that needs a shared backlog, a board, and a record of what got done can use it — the software-specific parts, like sprints and story points, are optional.