Technology
Managing multiple tasks becomes challenging when teams do not have a clear view of what is pending, what is being worked on and what has been completed. Tasks may get delayed, responsibilities become unclear and team members may struggle to identify workflow bottlenecks.
A Kanban board helps solve this problem by displaying work visually. Teams can organise tasks into different stages, track progress and identify where work is getting stuck.
Jira provides built-in Kanban features that allow teams to create boards based on their project requirements. Whether you are managing software development, content production or daily business activities, learning how to set up a Kanban board in Jira can make work easier to coordinate.
Here is a step-by-step guide to getting started.
A Kanban board is a visual representation of tasks as they move through different stages of a workflow. Each task appears as a card, and team members move it across columns as work progresses.
A basic board may include:
Jira allows teams to customise these columns according to their processes. For example, a software development team may include separate stages for Development, Code Review and Testing.
The purpose is to make work visible so that everyone understands the current status of each task.
Start by signing in to your Jira account. From the project navigation or project creation area, select the option to create a new project.
Choose a Kanban template from the available project templates. Jira may offer team-managed and company-managed project options, depending on your account and permissions.
A team-managed project allows the team to manage many project settings independently. A company-managed project provides more centralised configuration and administration.
Enter a project name, review the settings and create the project. Once the setup is complete, Jira provides a workspace where you can organise tasks and manage the team's workflow.
If you already have a Jira project, you may be able to create a separate Kanban board without creating another project.
Navigate to the Boards section and select the option to create a board. Choose the Kanban board type and decide whether to create it from an existing project or a saved filter, depending on the options available.
If you create a board from an existing project, select the relevant project and provide a board name.
If you use a saved filter, ensure that it includes the issues you want to display. You may also need the appropriate permissions to create and share boards.
Once created, your board will display the issues that match its project or filter settings.
After creating the board, configure its columns to reflect how your team handles work.
For example, a content team may use:
A software development team may use:
In Jira, open the board settings and locate the Columns section. You can add, rename or rearrange columns based on your requirements.
Each column should represent a meaningful stage of work. If your workflow has too many columns, the board may become difficult to maintain. Start with the essential stages and add more only when they improve visibility.
Also check how Jira statuses are mapped to the columns. A status that is not mapped correctly may cause an issue to appear in an unexpected location.
A board becomes useful when it reflects the team's actual work.
Create issues using the Create option in Jira. Add a clear summary, description, issue type, priority and assignee where appropriate.
For example, a website development team may create tasks such as:
Each task appears as a card on the board. Team members can open a card to review its details, add comments, attach files and update its status.
Clear task descriptions and ownership help prevent confusion during execution.
Work-in-Progress (WIP) limits define how many tasks can remain active in a particular workflow stage.
For example, a team may set a limit of three tasks in Development and two in Code Review. When a column reaches its limit, team members should focus on completing or unblocking existing work before pulling in more tasks.
Jira supports column constraints on Kanban boards, depending on the board configuration and available features.
These limits help teams reduce multitasking and identify stages where work is accumulating. They should reflect actual team capacity rather than being selected randomly.
Once the board is active, review it regularly to understand how work moves between stages.
Jira offers useful Kanban features and reports that help teams examine their delivery process.
Cumulative Flow Diagram: Shows how work items accumulate across different workflow stages over time.
Control Chart: Helps teams analyse cycle time and understand how long issues take to move through the workflow.
Quick Filters: Allow users to display selected issues based on criteria such as assignee, priority or issue type.
Use these features to identify delays, review workload distribution and discuss possible improvements with the team.
A well-maintained board should reflect the team's actual workflow. Follow these practices to keep it useful:
Setting up a Kanban board in Jira helps teams organise tasks, track progress and understand how work moves through different stages. From creating a project and configuring columns to setting WIP limits and reviewing reports, each step contributes to better workflow visibility.
Start with a simple board that matches your team's existing process. As you use it, review where tasks get delayed and make changes based on actual delivery challenges. A well-configured Jira Kanban board should make work easier to understand and manage.