How to Add a Status to a Column in Jira

If you have ever stared at a Jira board wondering why a status is not showing up under the right column — or why dragging a card does nothing — you are not alone.

Jira is used by over 65,000 companies worldwide, and it consistently ranks as the most popular project management tool among software and operations teams. Yet one of the most searched questions about it is deceptively simple: how do you actually add a status to a column?

The answer involves understanding how Jira connects workflows to boards — and once you see it, everything clicks. This guide walks you through it from start to finish.

What a “Status” Actually Means in Jira

Before you touch any settings, it helps to understand what you are working with.

In Jira, a status is a stage in your workflow — things like “To Do,” “In Progress,” “In Review,” or “Done.” These statuses live inside a workflow, which is a sequence of steps attached to your issue types (tasks, bugs, stories, etc.).

A column on your Jira board is simply a visual container. Each column can display one or more statuses. So when you “add a status to a column,” what you are really doing is mapping a workflow status to a visible column on the board.

This distinction matters because:

• Statuses are managed at the project workflow level
• Columns are managed at the board configuration level
• If a status does not exist in the workflow, it cannot appear in any column

According to Atlassian, teams that define clear workflow statuses report up to 28% fewer miscommunications on project handoffs. Getting this right is not just a cosmetic fix — it directly impacts how clearly your team tracks progress.

The Two Ways Jira Boards Work (And Why It Matters)

Jira has two main board types, and the process for adding a status differs slightly between them.

Company-managed projects (formerly “classic projects”) give you full control over workflows and board configuration. Admins can create new statuses, build custom workflows, and map them freely.

Team-managed projects (formerly “next-gen projects”) have a simplified setup. You can add statuses directly from the board without touching the workflow editor.

Knowing which type your project uses saves you 20 minutes of searching in the wrong menus. To check: go to your Project Settings and look for the “Project type” label near the top.

How to Add a Status to a Column in a Team-Managed Project

This is the simpler of the two paths. Jira makes it almost drag-and-drop.

Step 1 — Open your board

Navigate to your project and click Board in the left sidebar.

Step 2 — Click “Manage workflow”

You will see a “Manage workflow” button at the top right of your board. Click it. This opens the inline workflow editor directly on your board view.

Step 3 — Add a new status

At the end of your existing columns, you will see a “+ Add status” button. Click it, type the name of your new status (e.g., “Awaiting Approval”), and press Enter.

Step 4 — Assign the status to a column

Jira automatically creates a new column for new statuses in team-managed projects. You can then drag and reorder columns as needed.

Step 5 — Save your workflow

Click “Update workflow” to confirm the changes. Your new status column is now live on the board.

How to Add a Status to a Column in a Company-Managed Project

This path involves two parts: first adding the status to the workflow, then mapping it to a column on the board.

Part 1 — Add the Status to Your Workflow

Step 1 — Go to Project Settings

In your project, click Project Settings at the bottom of the left sidebar.

Step 2 — Open Workflows

Under the “Issue types” or “Workflows” section, find the workflow associated with your issue type. Click the pencil (edit) icon next to it.

Note: If the workflow says “Read-only,” it is a shared system workflow. You will need to copy it first (Jira gives you a “Copy” button for this). Always edit a copy — never the original shared workflow.

Step 3 — Add a new status

In the workflow editor, click “Add status”. A dialog box opens. You can either:

• Choose an existing global status from Jira’s library
• Create a brand new one by typing the name and selecting a status category (To Do, In Progress, or Done)

Step 4 — Add transitions

A status without transitions is a dead end. Add at least one transition into the status (from another step) and one transition out (to the next step). Click “Add transition”, choose the source status, the destination, and give it a name like “Send to Review.”

Step 5 — Publish the workflow

Click “Publish draft” or “Save” at the top of the editor. The status is now part of your workflow.

Part 2 — Map the Status to a Board Column

Adding the status to the workflow is only half the job. Now you need to make it visible on your board.

Step 1 — Go to Board Settings

From your board, click the three-dot menu (or the gear icon) at the top right and select “Board settings.”

Step 2 — Open the Columns tab

In the board settings sidebar, click “Columns.” You will see your current columns and the statuses mapped to each one.

Step 3 — Add your new status to a column

Scroll to the column where you want the status to appear. Click “Add status” within that column. A dropdown will show all unmapped statuses — select the one you just created.

Alternatively, if you want the status to live in its own column, click “Add column” at the top, name it, and then drag your status into it.

Step 4 — Save changes

Changes to board settings save automatically in most Jira configurations. Refresh your board to confirm the column appears.

Why Your Status Might Not Be Showing Up (Common Fixes)

Even after following the steps above, some teams run into the same snags. Here are the most common ones.

The status is unmapped. If a status exists in the workflow but is not assigned to any column, issues in that status become invisible on the board. Go to Board Settings → Columns and look for a gray “Unmapped Statuses” section at the bottom. Drag any statuses from there into the appropriate column.

You edited the wrong workflow. Company-managed projects often have multiple workflows — one per issue type. If you added the status to the Bug workflow but you are looking at the Story board view, it will not appear. Double-check you edited the workflow tied to the right issue type.

The workflow is shared and you did not save a copy. Jira blocks edits to shared workflows to protect other projects using them. If you hit a read-only warning, click “Copy,” make your edits on the copy, and then reassign the issue type to use the new workflow.

Board filter is excluding issues. If your board has an active filter (common in Scrum boards), some issues and their statuses may be filtered out. Check your board’s “Saved Filters” in settings to confirm the query includes all issue types you expect.

How Teams Use Custom Statuses to Speed Up Work

Adding statuses is not just housekeeping. Done right, it is a workflow design decision that affects how fast your team moves.

Research from the Project Management Institute shows that organizations with defined and consistently followed processes are 28% more likely to deliver projects on time. Custom Jira statuses are one of the most direct ways to operationalize that kind of clarity.

Some high-performing teams use statuses like:

• “Blocked” — to surface stuck work immediately without needing a stand-up
• “Waiting on Client” — to distinguish internal delays from external ones
• “Ready for Deploy” — to create a clean handoff point between teams
• “QA Passed” — to separate “we think it works” from “we confirmed it works”

Each of these is a single Jira status that eliminates an entire category of status-update meetings. Teams that implement these kinds of workflow checkpoints report saving an average of 4-6 hours per week in redundant update conversations.

Jira Workflow Best Practices to Keep in Mind

A few rules that prevent the most common long-term headaches:

Keep your status count reasonable. Jira supports unlimited statuses, but boards with more than 8-10 columns become hard to scan. Every status you add should represent a genuine handoff or decision point — not just a “nice to have.”

Align status categories with real stages. Jira groups statuses into three categories: To Do, In Progress, and Done. These categories drive reporting metrics like cycle time and lead time. Make sure your statuses are assigned to the right category or your team’s velocity reports will be skewed.

Use consistent naming across projects. If your team has multiple projects, try to reuse the same status names for equivalent stages. This makes cross-project reporting in Jira dashboards significantly cleaner.

Test transitions before publishing. In the workflow editor, use the “View as diagram” option to check that every status has a valid path in and out. Orphaned statuses with no transitions create issues that can get permanently stuck.

Document your workflow rationale. Jira lets you add descriptions to statuses. A brief note explaining when something should move into each status saves hours of onboarding time when new team members join.

Conclusion

Adding a status to a column in Jira is a two-part process: first make sure the status exists in your workflow, then map it to the right column on your board. The exact steps depend on whether you are using a team-managed or company-managed project, but once you know where to look, it takes under five minutes.

The bigger opportunity is in using those statuses strategically — to create real handoff clarity, eliminate unnecessary meetings, and give your team a shared, real-time view of where every piece of work actually stands.

Teams that nail their internal workflows do not just move faster. They free up the mental bandwidth to focus on growth. And if growing your pipeline is on the agenda, that is exactly where a focused outbound strategy — built with precision targeting, tested campaigns, and a system that scales — makes the difference. SalesSo helps you build that system. Book a strategy meeting and we will show you how.