How to Use Jira: A Beginner's Guide to Agile Projects

Quick Answer[a][b][c][d][e][f][g][h][i]

Teams should follow some specific steps to use Jira for Agile project management. The basic process for this includes:

• Set up a project: Find a Scrum or Kanban workflow on the basis of your team’s requirements.
• Organize work: Develop and prioritize tasks, user stories, and bugs in the backlog.
• Plan and execute: Schedule work into sprints or manage tasks through a continuous Kanban workflow.
• Check progress: Use boards, dashboards, and reports to monitor task status and identify bottlenecks.
• Review and improve: Assess the outcomes of the project and refine workflows based on team feedback.

Jira allows Agile teams to centralize work management, improve visibility, and coordinate project activities from planning to delivery.

Key Highlights: How to Use Jira?

• Understand Jira: Discover what Jira is, who uses it, and how it helps Agile project management.
• Create your first project: Select a template, open issues, and begin to organise work into manageable chunks.
• Manage Agile workflows: Create a backlog, plan a sprint, update boards, and monitor project progress.
• Use Jira for your work: Learn what developers, testers, Scrum Masters, and Product Owners are doing in Jira every day.
• Search smarter with JQL: Write simple JQL queries to find issues and track work.
• Use Jira on an actual project: Learn how to go from starting a project to sharing reports and delivering.

Introduction

Think of a software project where developers are waiting on requirements, testers are reporting bugs through chat messages, and project managers are confused about what is late. Without a central system, it can be hard to coordinate even a small project.

That’s where Jira can help.

Atlassian's Jira is a work management and issue tracking platform that allows teams to plan work, track work, prioritize, assign work, handle issues, and monitor progress. Originally a popular tool for Agile software development teams, Jira is also used for coordinating business projects, service requests, and operational work.

You don't need to learn all of Jira immediately. First of all, it's good to understand how projects, issues, boards, workflows, and reports fit together. Once you're familiar with these concepts, you can start investigating Jira Query Language (JQL), automation, and custom dashboards.

Follow this beginner's guide to JIRA, if you are a developer, tester, product owner, Scrum Master, or project coordinator. You will discover the ways to  define your project, organize your daily work, and see improvements with JIRA.

What Is Jira and Who Uses It?

Jira is a project management and issue tracking tool that enables teams to organize work from planning to delivery. It provides a common place to capture tasks, assign responsibility, prioritize, track status, and review progress.

Jira is the tool for 2 of the most popular practices used by Agile teams: Scrum and Kanban. Scrum teams plan work in time-boxed sprints. Kanban teams plan work with a continuous flow of work items across a board.

Atlassian products such as the documentation tool Confluence and source code manager Bitbucket. The combination of products and their setup will vary depending on what integrations teams are able to connect to.

Who uses Jira?

Different experts use Jira for different use cases. This includes:

Developers: Itemize requirements into tasks, follow the progress of implementation work, and tie code changes back to the issues.

Testers and QA engineers: Log defects, associate bugs with features, and see status of testing.

Scrum Masters: Coordinate sprint planning, provide team feedback, and uncover workflow bottlenecks.

Product Owners: Focus on backlog grooming, user story refinement, and communicating product needs.

Project managers: Follow ownership, deadlines, dependencies, and delivery.

Business teams: Manage requests, approvals, marketing programs, and other formal processes.

For instance, if you're developing an online shopping application, you might use Jira to storyboard a checkout functionality, create issues for paying problems, and keep a record of the work that needs to be finished up prior to releasing the app.

The core value of Jira is that it takes information about work and puts it in a shared place, rather than having key information stuck in spreadsheets, emails, and chat threads.

Key Jira Terms Beginners Need to Know

Before starting a project, it helps to understand the terminology used throughout Jira. These concepts form the foundation of most Jira workflows. Atlassian has also introduced work as the new collective term for items tracked in Jira, so you may see “work item” in newer versions where this guide says “issue”.

These terms are related. A project has issues, an epic can group work of a related nature, and a board shows selected issues as they move through a workflow. In Scrum, a team uses a backlog to choose work for a sprint.

For example, the epic Checkout Improvements could have a story about secure payments, a task to set up a payment gateway and a bug about a failed transaction. Understanding this hierarchy will make it easier to navigate Jira and communicate with your team.

How to Use Jira: A Step-by-Step Beginner's Guide

The best way to learn Jira is to build a little sample project and then use that project to perform common tasks. Here are the steps from creating a project through reporting progress.

Create Your First Jira Project and Choose a Template

First, you will need to create a project that works the way your team does.

• Sign in to your Jira account.
• Go to your Projects menu and check if there's an option to create a project. Depending on your Jira version and permissions, you may find it under a different name or location.
• Choose a suitable project template.
• Add a project name, for example, Online Shopping App.
• Check through the different project options and access provided.
• Make the project and get the board or work view of it.

Jira does the job for a rather basic structure, so there is no need for you to start from the ground up. Use a Scrum template for a team that uses sprints and does sprint planning, review, and retrospective sessions.

The best way to learn Jira is to create a small sample project and use it to practice common activities. The following steps explain how to move from project setup to progress reporting.

Create Your First Jira Project and Choose a Template

Your first step is to create a project that matches the way your team works.

1. Sign in to your Jira account.
2. Open the Projects menu and look for the option to create a project. The exact label and location may vary by Jira version and permissions.
3. Choose a suitable project template.
4. Enter a project name, such as Online Shopping App.
5. Review the available project settings and access options.
6. Create the project and open its board or work view.

Jira templates generally provide a basic structure, and you don’t need to set up everything from scratch.

Choose a Scrum template if your team works in sprints and does sprint planning, sprint reviews, and retrospectives. If your team has a constant flow of work and you want to see tasks moving toward completion, try a Kanban template.

There are different configuration options for some Jira project types. For a beginner, a simple template with the required statuses and issue types is mostly enough. Example in action: A team building a mobile banking app, for instance, can choose a Scrum template because it offers enhancements in planned iterations. Kanban can be used by a technical support team that handles incoming requests continuously.

Need to compare deployment types? Read this guide to Jira Cloud vs Jira Server.  Note that Jira Server is at the end of support. For teams considering self-managed deployments, consider also Atlassian's Data Center and current Cloud offerings.

Create and Write Effective Jira Issues

Once the project is ready, create issues to represent the work that needs to be done. In most views of Jira projects, the Create option displays an issue form. Select the correct project and issue type, enter a summary, write a description, and complete all relevant fields.

Common issue types are stories, tasks, bugs, and epics. The types available to you depend on your project configuration. A useful Jira issue should answer four questions:

• What needs to be done?
• Why does it matter?
• Who is responsible?
• How will the team know it is complete?

Consider the difference between these two task descriptions:

Vague issue: Improve checkout.

Clear issue: Add validation for expired payment cards and display an error message before the customer submits the payment.

The second description provides a clearer scope and expected outcome.

For user stories, a common format is:

"As a [type of user], I want [an action or capability] so that [a benefit]."

For example:

"As a customer, I want to save my delivery address so that I can complete future purchases faster."

You can add acceptance criteria to clarify when the story is complete:

• Customers can save a valid delivery address.
• Required address fields are validated.
• Saved addresses appear during checkout.
• Invalid or incomplete addresses generate an understandable message.

Assign the issue to the right team member, set a priority, add a due date if needed, and link related issues where helpful. Don’t just fill in every optional field just because it’s there. “The goal is to make work transparent and actionable.

Build and Prioritize the Backlog

A backlog is a prioritized list of work that the team may complete in the future. It gives the team a structured way to decide what deserves attention first.

To build a useful Jira backlog:

1. Add the stories, tasks, and bugs that represent planned work.
2. Group related issues under epics where appropriate.
3. Review each issue for clarity and completeness.
4. Estimate effort if your team uses story points or another estimation method.
5. Arrange issues in priority order.
6. Identify dependencies, risks, and work that requires clarification.

The prioritization should take into account factors such as customer value, urgency, risk, dependencies, and implementation effort. Exactly how will depend on what the team wants to do.

For example, a missed payment that affects many customers should generally be considered more important than a small visual upgrade. It may also be worth considering early on a task that blocks several other tasks.

Keep the backlog tight. Get rid of duplicates, close old issues, and break large stories into smaller chunks that can be completed and reviewed. Backlog refinement is a process to help Scrum teams prepare work for the upcoming sprints.  A well-governed backlog removes the uncertainty from sprint planning and makes it easier to have conversations about realistic commitments.

Plan and Run a Sprint

A sprint is a fixed period during which a Scrum team works toward a specific goal. Many teams use one- or two-week sprints, although the appropriate duration depends on their working practices.

How to plan a sprint in Jira:

• Open the Scrum board's backlog.
• Review the highest-priority issues.
• Verify that the work was understood adequately.
• Estimate effort if your team uses estimates.
• Move suitable issues into the sprint.
• Decide upon a sprint goal that states what you hope to achieve.
• Start the sprint and confirm its duration.

For example, you might have a sprint goal of making checkout more reliable. You may focus on payment validation, error messages, transaction testing, and much, much more.

The team has to take into consideration the capacity, planned time off, dependencies, and the capacity completed in the previous sprints.

Move Work Through the Jira Board and Workflow

A Jira board displays issues according to their current status. It gives team members a shared view of work that is waiting, in progress, blocked, or completed. A simple workflow might contain these statuses:

To Do → In Progress → In Review → Done

A testing team could use a different workflow:

Open → In Development → Ready for Testing → Testing → Closed

The statuses and transitions available depend on the project's workflow configuration.

Open an issue or select it from the board, and update its status with the available transition, or use drag-and-drop interaction. Add comments to capture important decisions, blockers, or handoffs.

For example, when a developer completes payment validation, the issue could move from In Progress to In Review. Once the code review is approved, it can transition to Ready for Testing.

A board is more useful when a team has agreed on what each status means. If one person marks a task as done and another person is waiting for testing and approval, the board will show an inconsistent view of progress.

Where supported, teams can also use work-in-progress limits to discourage starting too many tasks at the same time. If your team is working in a continuous-flow way, check out this guide to the Kanban board to see how visualizing work can help you identify bottlenecks.

Track Progress With Reports and Dashboards

Jira reports and dashboards give teams an understanding of delivery progress, workload, open issues, and recurring problems. Depending on the project type and configuration, useful reporting options might be:

• Burndown chart: A chart that depicts the work left in a sprint against the planned timeline.
• Sprint Report: Summary of work completed and not completed in the sprint.
• Velocity chart: Shows how much estimated work a team completes over sprints, if estimation is set up.
• Cumulative flow diagram: Shows how much work is distributed across workflow stages over time.
• Control chart: A tool to help teams look at cycle time and variation in delivery (see lead time vs cycle time).
• Issue Statistics: Summary of issues by fields like status, assignee, or priority.

Dashboards can collate several useful views. For example, a project manager might want to track overdue high-priority issues, unresolved bugs, sprint progress, and recently updated work all in one place.

The usefulness of a report depends on the consistency of the issue data behind it. If team members don’t update statuses or don’t record estimates correctly, charts can give a misleading picture.

Don’t use a single metric in isolation. Teams that complete more story points are not necessarily delivering more value to the customer. Combine the numbers with a discussion of quality, risks, dependencies, and deliverables.

How to Use Jira for Scrum vs Kanban

Jira supports both Scrum and Kanban workflows, but they organize work differently.

Using Jira for Scrum

Scrum teams use Jira to organize a product backlog, plan sprints, assign or choose work, and review the results of the sprint.

So, for example, a product team might decide to spend two weeks on a sprint to improve the checkout experience. The team selects stories to work on, sets a sprint goal and uses the board to track progress.

At the end of the sprint, the team looks at what was done and discusses how they can improve for the next iteration.

The Scrum Master can review Sprint reports and activity on the board for work that is blocked, surprises, or delivery issues that keep recurring.

Using Jira for Kanban

Jira helps Kanban teams visualize work in a flow that never stops. Issues progress through agreed stages, not necessarily in fixed-length sprints.

For example, an IT operations team might use statuses such as New, In Progress, Waiting for Information, and Resolved to triage incoming incidents.

Work-in-progress limits can help prevent the team from starting more work than it can reasonably handle. Flow metrics can then reveal where tasks spend the most time waiting.

Which approach should you choose? If your team could benefit from time-boxed planning and regular sprint reviews, then choose Scrum. Kanban – If work is constantly flowing in and the team needs to manage flow and shifting priorities. Some other teams use a hybrid process, but it should be transparent for everyone involved.

How to Use Jira by Role

Jira is a shared workspace; however, members of the team use it differently. By learning these role-based workflows, you can focus on the features that are relevant to the responsibilities that you perform.

How Developers Use Jira

Jira is used by developers to get requirements, decompose implementation work, track progress, and coordinate with other team members.

A typical development workflow consists of:

• Read the assigned story or task.
• Read the description and the acceptance criteria.
• Look for related problems, dependencies, and relevant documentation.
• Start the implementation update issue.
• If your team’s development tools allow, associate the issue with a branch, commit, or pull request.
• Get the issue through code review and then test it.
• Record relevant technical notes and close the issue when the agreed criteria are met.

For example, a developer working on a password-reset feature might create an implementation task that is linked to the parent story and note a dependency on the configuration of the email service.

This allows reviewers and project stakeholders to see how the individual tasks fit into the larger feature.

How Testers Use Jira for Bug Tracking

Jira can help QA teams document defects, assign them to developers, track fixes, and confirm whether issues have been resolved.

To use Jira for bug tracking:

1. Create a bug issue.
2. Write a specific summary describing the observed problem.
3. Record the environment, such as browser, operating system, or application version.
4. Document the steps to reproduce the issue.
5. Include expected and actual results.
6. Add screenshots, logs, or other evidence when appropriate.
7. Set the priority and assign the bug according to the team's process.
8. Link the bug to the affected story or epic.
9. Retest the fix and update the issue's status.

Example bug report

• Summary: Payment fails when a customer submits an expired card.
• Environment: Staging environment, supported desktop browser.
• Steps to reproduce: Open checkout, enter an expired card, and select Pay.
• Expected result: The application displays a validation message and prevents the transaction.
• Actual result: The checkout page displays a generic error.
• Priority: Set according to customer impact and the team's severity guidelines.

This structure enables the developer to reproduce the issue without asking the tester for missing information again and again.

If your team is trying to learn how to use Jira for testing, the most important thing is to link your testing activity to the relevant requirements and defects. Jira can track testing-related tasks and bugs; however, for items such as detailed test cases, test cycles, and specialized test execution reports, you may need to consider dedicated test-management apps or integrations.

How Scrum Masters Use Jira for Sprint Management?

Scrum Masters assist teams in understanding and iterating on their ways of working. They are supported by Jira in providing information for sprint planning, daily stand-ups, sprint reviews, and retrospectives.

A Scrum Master can use Jira to:

• Review the backlog before sprint planning.
• Help the team clarify priorities and dependencies.
• Confirm that the sprint goal is understandable.
• Monitor blocked or aging issues.
• Look over sprint reports and updates to proposed work.
• Facilitate conversations about unfinished work.
• Identify recurring bottlenecks and improvement opportunities.

A new coach might notice that multiple issues remain in code review for days. They can coach the team to understand why this happens. Is it because the reviewers are unavailable? Are they unclear what they need to do in review? Or is it because they have too many issues in progress? Jira reports are great for review, but they can't replace collaborating or automatically discovering the root cause.

Therefore, the practical Jira tutorial on Scrum Master learning should be backlog managing, sprint creation, board creation, reporting, and facilitation skills to translate observations into changes. CSM certification can be an option if you want to strengthen your Scrum expertise and gain an idea about other Scrum Master training and certification avenues.

How Product Owners Use Jira for Backlog Management

Product Owners use Jira to organize product requirements, communicate priorities, and help the team focus on valuable outcomes.

Typical activities include:

• Creating and refining user stories.
• Defining acceptance criteria.
• Grouping related work under epics.
• Prioritizing features and defects.
• Clarifying business requirements.
• Reviewing dependencies and delivery risks.
• Discussing scope changes with stakeholders.
• Monitoring whether delivered work meets the intended outcome.

For example, suppose a product owner is working on a travel booking application. He may decide that a reliable payment flow is more important than a cosmetic change, because payment failures affect customers trying to complete a booking.

Jira does show the order of priority, but the Product Owner still needs to explain the rationale behind decisions and work with the development team.

A well-maintained backlog should reflect current product priorities and not be a storehouse for every idea ever suggested.

How to Search Jira Issues With Basic JQL

Jira Query Language (JQL) enables users to search for issues using conditions that are more specific than a simple keyword search.  It is very useful for projects with many tasks, bugs, and stories.

Depending on your version and permissions, you can usually get to a more advanced issue search from within the Jira issue search interface and switch to JQL mode.

Here are some useful examples.

Replace SHOP with your actual project key and 12 with the relevant sprint ID. Field names, issue types, statuses, and available operators may vary depending on your Jira configuration.

Understanding basic JQL operators

These are some of the most useful elements to learn first:

• = matches a field to a specific value.
• != excludes a specified value.
• AND requires both conditions to be true.
• OR accepts either condition.
• IS EMPTY checks whether a field has no value.
• >= and <= compare values or dates.
• ORDER BY sorts the matching results.

For example:

project = SHOP AND issuetype = Bug AND statusCategory ! = Done ORDER BY priority DESC

The query finds bugs in the SHOP project that are not in the Done status category and sorts them by priority in descending order.

JQL generally does not update issues but finds issues that match the criteria. You can save useful searches as filters and use them in dashboards or other Jira views (where supported).

Begin with a simple query and then add one condition at a time. This facilitates the detection of errors and helps to understand how some problems arise in the results.

Jira Example: Manage a Simple Project From Start to Finish

Let us see how these concepts work together as we run a fictitious online shopping project.

The aim is to enhance the reliability of the checkout so that users are able to complete payments without experiencing unnecessary validation errors.

Step 1: Create the project

Make a Jira project called Online Shopping App and select a Scrum template if the team wants to complete work in sprints.

Assume the project key is SHOP.

Step 2: Build a story epic

Create an epic called Checkout Improvements.

The epic is the bigger picture or, finally, groups the stories and tasks related to checkout reliability.

Step 3: Add a story

Write a story below the epic:

As a customer, I want to see clear messages about the state of payment validation so I can fix errors and complete checkout.

Include acceptance criteria for expired cards, incorrect payment details, and a clear message in case of error.

Step 4: Break the story into tasks

Derive smaller tasks for implementation and verification:

Implement payment-card validation.

Display appropriate validation messages.

Add unit tests for invalid payment details.

Verify the checkout flow in the staging area.

If testing uncovers a defect, raise a bug issue for it. Connect related issues so the team can follow the problem and where the solution was implemented.

Step 5: Planning the sprint

At the sprint planning, examine the backlog, interpret the scope, and choose the backlog items that the team thinks it will be able to complete to achieve the sprint goal.

The goal of the sprint could be to enhance checkout validation and to learn how to cut down on avoidable payment errors.

The team should test the plan, considering capacity, dependencies, and testing needs, before sticking to it.

Step 6: Track work on the board

Transition: Issues go from To Do to In Progress when developers start to work on them. Issues go from in progress to review or testing once they are coded.

In case a defect is found during a test, the tester files a bug against the story that is affected. The developer rectifies it, and then, the tester verifies the result.

Step 7: Look over reports

Audit the report, the correct board data at the end of the sprint, etc.

Questions to ask:

• What issues were finished?
• Which issues remain unfinished?
• What were the barriers?
• Did the team meet the sprint goal?
• What should change during the next sprint?

The following flow summarizes the example:

Project → Epic → Story → Task → Sprint → Board → Reports

Each level has a purpose. The project organizes the work. The epic defines a larger body of work. The story describes a user outcome. The task is an actionable piece of work. The sprint is a planning window. The board tracks progress. Reports support review and improvement.

This example shows how to use Jira for project management without any advanced setup. When the basic flow is working, the team can start to look into automation, saved filters, integrations, and more detailed reporting.

Common Jira Mistakes New Teams Make

Jira can provide a clear view of work, but poor practices can make the system difficult to maintain. New teams should watch for the following mistakes.

1. Creating issues with vague descriptions

Issues such as "Fix checkout" or "Improve performance" don’t give team members enough information to act confidently.

How to avoid it: Include context, expected behavior, acceptance criteria, and reproduction steps where relevant.

2. Using too many statuses

A workflow with numerous overlapping statuses can make it difficult to understand where work stands.

How to avoid it: Start with a small number of meaningful statuses and add complexity only when the process genuinely requires it.

3. Treating Jira as a task dump

Creating issues without reviewing, prioritizing, or closing them leads to a backlog filled with outdated work.

How to avoid it: Schedule regular backlog refinement and remove duplicate or obsolete issues.

4. Starting too much work at once

When there are too many tasks in progress at the same time for team members, work can pile up and important things can take longer to complete.

Avoiding: Make current priorities visible. Agree on expectations for work-in-progress. Complete existing work before starting new work where practical.

5. Ignoring dependencies and blockers

A task may remain stalled because it depends on another team, an approval, or an external service.

How to avoid it: Link related issues, record blockers, and raise dependencies during team discussions.

6. Failing to update issue status

If work is marked "In Progress" when it is completed, reports and dashboards are useless.

How to prevent it: Make status updates a normal part of the team’s working routine, not just an administrative task done right before meetings.

7. Misusing estimates and metrics

Story points and velocity are planning tools, not universal measures of productivity for any one individual.

How to avoid it? Use metrics to know trends and improve the team's process. Think about the numbers, but also about quality, customer results, and delivery risks.

8. Customizing everything too early

Excessive custom fields, complex workflows, and unnecessary automation can make Jira harder to learn.

How to avoid it: Begin with a standard template, validate the team's workflow, and introduce customization only when there is a clear need.

Your First-Week Jira Setup Checklist

Use this checklist to establish a practical Jira routine during your first week.

Day 1: Set up the basics

• Confirm your Jira access and project permissions.
• Create a project using a suitable template.
• Identify the board and the available issue types.
• Learn how to create, edit, assign, and search for issues.

Day 2: Organize the work

• Create a few sample stories, tasks, and bugs.
• Write clear descriptions and acceptance criteria.
• Group related work under an epic where appropriate.
• Agree on the meaning of each workflow status.

Day 3: Prepare the backlog

• Review and prioritize planned work.
• Remove duplicate or obsolete issues.
• Identify dependencies and blockers.
• Estimate work if your team uses estimation.

Day 4: Practice the workflow

• Move sample issues through the board.
• Add comments and link related issues.
• Practice reporting a bug with reproduction steps.
• Confirm what the team considers complete.

Day 5: Explore planning and reporting

• Review sprint planning if you use Scrum.
• Learn how your team selects and starts a sprint.
• Open the available reports and dashboards.
• Try a basic JQL query.
• Identify one improvement for the team's Jira workflow.

By the end of the week, you should be familiar with the day-to-day actions needed to create issues, update work, find information, and understand basic project progress.

You don’t need to know how to handle all Jira features right away. Learn the basics, get confident, and then as your responsibilities grow, get into more complex searches, automation, integrations, and reporting.

Conclusion

Jira becomes easier to learn when you think of it more as a workflow tool and less as a list of menus and features. Make a project, write clear issues, organize the backlog, and move work through a simple board. Then find out how to plan sprints or manage continuous flow, find issues with JQL, and track progress with reports and dashboards.

The most important thing is to be persistent. A well-maintained Jira project provides a common understanding of priorities, ownership, blockers, and progress to everyone. A poorly maintained one quickly becomes another place where information goes out of date.

If you’re new to Agile project management, try these steps out with a small sample project before adding more complex workflows. With the improvement of your skills, you can go for structured training on Jira software to enhance your knowledge regarding issue tracking, Agile boards, reporting, and project configuration.

If you use it regularly and have a clear process for your team, Jira can become a very useful part of your daily project management routine.