What is a Jira Board?

Key takeaways
A Jira space holds work items, while a board displays and helps manage a selection of that work.
Scrum boards organize work around fixed-length sprints; Kanban boards emphasize continuous flow and work-in-progress limits.
Board columns represent workflow stages, while swimlanes group work horizontally by a category such as workstream or user.
Company-managed spaces support multiple boards and cross-space boards for different teams, workstreams, or shared views.
A Jira board is a visual tool or view used to manage work items as they move from creation to completion, shown as cards that move across columns. Each card is a work item and each column is a stage in your process.
This provides the entire team with a shared, at-a-glance view of what is being worked on and where it stands. You can find your board in the sidebar navigation under "Board.”
Boards are flexible and work for almost any kind of team, not just software teams. Teams that practice scrum use the board to display a prioritized selection of work committed to a sprint.
On the other hand, teams that practice Kanban use it to move every work item through the columns from creation to completion.

How does a board differ from a space in Jira?
A Jira space houses all work items needed to achieve a particular goal. A Jira board, on the other hand, is the tool used to manage those work items as they move from creation to completion.
In short, the space holds the work, and the board is how you visualize and move it.

What types of Jira boards are available?
Jira offers two boards with features that help teams start practicing Agile methodologies and track their work. Both come pre-configured and ready to use with Jira templates.
Scrum board: Ideal for teams that work in sprints, the time-boxed periods when a team completes a set amount of work.
Kanban board: Works well for teams whose main objective is to manage the flow of work, visualizing and prioritizing tasks as they go.
Scrum board vs. Kanban board: What is the difference?
The boards can look similar, but scrum and kanban differ in practices and key features. This comparison shows how they line up.
Aspect | Scrum board | Kanban board |
Best for | Teams that plan work in fixed sprints | Teams that manage a continuous flow of work |
Ideology | Learn through experience and reflect on wins and losses to improve | Use visuals to understand capacity and improve work in progress |
Cadence | Regular, fixed-length sprints (for example, two weeks) | Continuous flow |
Key features | Insights, backlog, and sprints | Configurable columns and work in progress (WIP) limits |
Backlog is home to all of your team's potential work items for the project.
Sprint is a time-boxed period when a scrum team completes a set amount of work. You create a sprint, define its goals, and add work items from the backlog.
Columns each represent a step in the workflow, and you configure them to reflect your team's process.
WIP limits cap how many cards can sit in a column at once, helping the team spot bottlenecks in the delivery pipeline.
Which Jira board should you use?
Use a scrum board if your team plans work in sprints and commits to a set amount of work per cycle. Choose a kanban board if work arrives continuously and you want to manage flow and limit work in progress.
Many teams start with one and adjust as their process changes. You can learn more about kanban vs scrum in our complete guide.
What are multiple and cross-space boards?
Multiple and cross-space boards are available in company-managed spaces.
In Jira, you can create multiple boards within a single company-managed space, where each board shows only the work items that meet your criteria. Common use cases include:
Different work streams within a single space. A board for each work stream makes work easier to track and manage.
Multiple teams working on a single project. Each team can have its own board configuration and workflow.
Lengthy processes with various stakeholders. A board for each part of a long workflow makes the stages easier to manage.
You can also create cross-space boards that pull work items from multiple spaces. Common use cases include:
Summary view for leadership. A cross-space board gives an overview across multiple teams and projects.
A team that works across multiple spaces. For example, a development team deploying software that touches several spaces.
Security reasons. A cross-space board can surface the right work items while keeping other spaces private.
What are swimlanes in a Jira board?
A swimlane is a horizontal categorization of work in the active sprints of a scrum board or on a kanban board. You can use swim lanes to organize tasks by category, such as workstream, user, or application area, so the board stays easy to read.
How do AI agents work with Jira boards?

You can bring AI agents onto a board the same way you bring in a teammate. There are three main ways to put an agent to work, and each keeps the work visible and reviewable:
Assign a work item to an agent: Add an agent in the assignee field, and it starts on the task using the work item's context. You review the output before the work moves on.
Add an agent to a column: When any work item moves into that column, the agent starts working on it automatically.
Trigger an agent on a workflow transition: An agent can run through automation when work moves from one status to another, so routine steps happen without manual effort.
The board shows which items are with an agent and what state each one is in, and all agent activity is recorded on the work item. Agents work within Jira's existing permissions, so their work stays governed and visible.
New to Jira? Start with the introduction to Jira. Want to get started today? Sign up for free!
What other views exist in Jira?
Get a quick breakdown of all the Jira views, how they work, and the best ways to fit them into your workflow.
Boards are one of several ways to see your work in Jira, and different views suit different jobs.
A list gives you a spreadsheet-style view of work items and their fields,
A timeline maps work against dates so you can plan across weeks or months
A calendar shows due dates and scheduled work at a glance
A backlog holds and prioritizes upcoming work.
Because every view draws on the same underlying work items, you can move between them without duplicating anything and pick the one that best answers the question in front of you.
Jira Boards: Frequently asked questions
What is a Jira board used for?
Can AI agents work on a Jira board?
Are Jira boards only for software teams?
Can you customize the columns on a Jira board?
Recommended for you
Guide to Jira Work Items
Learn how to review work item types and relationships in Jira to make search conditions easier to interpret.
Guide to Jira Reports and Dashboards
Track progress, spot blockers, and share real-time reports with Jira dashboards built for your team.
Guide to Jira Plans
Build roadmaps, plan across teams, map dependencies, and balance capacity in one view with Jira Plans.