On this page
Kanban Status Board shows a Jira project as a Kanban board with one column per workflow status. Drag a card to another column and the real transition runs in Jira — statuses your workflow can’t reach are blocked while you drag.
Drag and drop across real workflow statuses
One column per status of each issue type’s workflow, coloured by status category, with one board per issue type. Dropping a card runs the transition with your permissions; if it needs a field such as a resolution, the message names it.
WIP limits, swimlanes and sums
Set a WIP limit per column — it turns red over the limit. Split the board into swimlanes by assignee, epic, priority or project, and sum Story Points, original or remaining estimates per column.
WIP aging and throughput
Every card in progress shows how many days it has spent in its status. The day count turns amber once a card has been there longer than half of the project’s finished issues took in that status, and red past what 85 % of them took (issues finished in the last 90 days). Until five issues have finished, it stays grey and says why.
Flow metrics in the toolbar opens two charts: WIP aging, one dot per card in progress by status and age with the 50 % and 85 % lines (click a dot to open the issue), and throughput, issues finished per week over the last 12 weeks with the average, the last 4 weeks and this week so far. Both are worked out from Jira’s status history when the board opens; nothing is stored. Turn them off in View settings.

Views for every way you work
Add view tabs by priority, assignee, due date, sprint, component, label or any select field. Save filters as profiles, share a view with the whole project and link to it.
Also included
- Bulk move with undo — select several cards, move them at once; Ctrl+Z brings them back.
- Card fields — parent, status, due date, labels, components, fix versions, remaining estimate.
- Faster start — fewer requests and less code to load when the board opens.
- Rank like Jira’s boards — Move up / Move down stores Jira’s rank (Jira Software).
- Filters and quick find — Only my issues, assignees, statuses, issue types, priorities, created date; Mine and Unassigned.
- Inline summary edit and reassign from the card; full keyboard navigation.
- Export to CSV, a dashboard gadget, auto-refresh and Jira’s dark theme.
Runs on Atlassian
Kanban Status Board is built on Atlassian Forge. Transitions run as you, with your Jira permissions and workflow rules. Flow metrics read the issues’ status history with your permissions and are not stored. The app stores only your profiles and views inside your Atlassian site and makes no external calls. See the privacy policy.
Related apps
- Priority Board — prioritize the backlog by dragging issues between priority columns.
- Deadline Tracker — overdue and upcoming work across projects on one board.
- Workload & Capacity Planner — see who is overloaded, and in which week.
Which story point field your space uses, and why a board can count 0: Jira story points, tested. What Jira’s control chart counts as cycle time, and how it differs from the age on our cards: Jira cycle time, tested. Running a Kanban team with people on leave? The ghost resource problem is worth a read. What each status and field on a ticket is for: Jira ticket explained. How the statuses, transitions and their rules fit together: Jira workflow. Why the columns are grey, blue or green, and which statuses count as done: Jira status categories. What Jira’s own kanban board does with a WIP limit (it warns, never blocks) and where Done items go: Jira kanban board, tested. Labels or components for the By label and By component tabs, and what Jira does with each: Jira labels vs components, tested.
Frequently asked questions
Which Jira permissions does the app ask for, and why?
Read and write Jira work, to search issues and change the due date, priority, assignee or status as you; read Jira users, for people in the filters; app storage, for saved views; manage Jira configuration, only because Jira requires it to list the members of a group for the Groups filter; and Jira Software board and sprint permissions for the Sprints view and rank. Every change is made with your own permissions.
Where is my data stored?
Saved views and filters are stored by Atlassian in the app's Forge storage for your site; issues stay in Jira and are changed from your browser, as you. The app makes no outside connections and Simplify has no server.
How much does it cost?
It is free for sites with up to 10 users. Larger sites pay per user through the Atlassian Marketplace, after a free 30-day trial.
Does dragging a card change the issue's status in Jira?
Yes. A drop runs the real workflow transition into that status, as you, with your workflow's conditions and validators. Statuses the workflow cannot reach are blocked while you drag.
What happens if a transition needs fields, such as a resolution?
The card goes back to its column and the message names the required field; open the issue to complete the transition there.
How does the board show work that is stuck?
Every card in an in-progress status shows how many days it has spent there. The day count turns amber once the card has been in that status longer than half of your recently finished issues took, and red past what 85 % of them took. Flow metrics in the toolbar opens a WIP aging chart and weekly throughput for the last 12 weeks.
Are WIP limits enforced?
They warn. A column over its limit turns red, but you can still move cards into it — as on Jira's own boards.
Do I need Jira Software?
No. Without Jira Software there is no Sprints view and no ranking; the status board, WIP limits, swimlanes, sums and views all work.
Where is my data stored?
Issues stay in Jira. The app stores only your saved profiles and views, in its Forge storage inside your Atlassian site; nothing is sent outside Atlassian.
Get Kanban Status Board for Jira
Free up to 10 users. Install it from the Atlassian Marketplace.