Jira is a software application developed by the Australian software company Atlassian that allows teams to track issues, manage projects, and automate workflows.

Key Jira concepts

Jira is based on four key concepts: issue, project, board, and workflow.


An issue is a single work item you track from creation to completion. An issue could be a bug, a user story, an epic, a to-do item for an HR team, or an artifact that your documentation team needs to create.

People may refer to issues as requests, tickets, or tasks. It’s better to use issues or the specific issue types that you define to avoid confusion.

Most product teams typically use issue types of Epic, Story, Bug, Test, and Task.


A project is a way to group your issues along with the common information and context that tie those issues together. You can configure issues associated with a project in a variety of ways, including visibility restrictions and applicable workflows.

When you use Jira to support your product development efforts, it’s helpful to have a single project for each product.


A board in Jira is a visual representation of your team’s workflow within a project. You can use multiple boards for flexible ways to view, manage, and report on work in progress on the same project.

If you use an agile approach, you may find it helpful to use a Kanban Board view to track backlog items as they refine and a Sprint Board to show the Sprint Backlog for your current sprint.


A workflow represents the path that issues take as they progress through your project from creation to completion.

Each label in a workflow, such as To Do, In Progress, and Done, represent a status that an issue can take. You can configure workflows to govern the transitions an issue can take between different statuses and trigger actions that occur when an issue moves into a status.