Board & timeline
Last updated: 17 November 2026
The Board is where Kanban+ spends most of its time, and it's the tab you land on. The Timeline draws the same board scope as a Gantt chart with dependency arrows, over its own window: anything updated in the last 90 days, finished or not. Both read live Jira data, and both write changes straight back to Jira as you — not as the app.
New to Kanban+? Start with Getting started.
What the board loads
The board runs one JQL query, assembled from the pieces you configure:
- the project clause from the board's projects
- the board's own Board filter (JQL), in Settings
- any quick filters you have switched on
- any field filters you've picked in the pill bar
- the board view's own condition:
resolution is EMPTY AND statusCategory != Done
For a board scoped to two projects with a filter of labels = frontend:
(project in (10001,10002)) AND (labels = frontend) AND (resolution is EMPTY AND statusCategory != Done) ORDER BY updated DESCResults are paged 100 at a time with no cap — a counter reads "Loading… N issues" while it works. A board with thousands of open issues will load all of them, so a board filter is worth setting.
The board refreshes itself every 60 seconds, and again when you come back to its tab. If someone changed an issue elsewhere in Jira, the cards update and a short toast says how many changed.
Finished issues
The board shows open work. An issue counts as finished once it has a resolution or sits in a Done-category status, and finished issues aren't loaded.
Any card you move or open during a visit is added to the query as OR key in (…), up to the latest 200 issues. So a card you drop into Done stays there through every background refresh, and leaves when you next load the page. If one of those issues is deleted in the meantime, Jira refuses the query, so the board lets go of them all and carries on. An issue someone else finishes leaves your board at the next background refresh, unless you moved or opened it during this visit.
Three things follow from this:
- A Done column starts empty on every page load. It only fills with issues you moved or opened during that visit.
- A reopened issue can stay hidden. If a workflow's reopen transition leaves the old resolution in place, the issue still counts as finished. Clear the resolution in Jira and it comes back. Fixing the transition stops this happening on the next reopen, but doesn't clear a resolution an issue already has.
- Sprint progress and Board Insights still count finished work. They run a separate search for finished issues updated in the last 30 days.
Columns
Columns are yours to define. Each one maps to one or more Jira statuses, so a column can absorb several workflow states.
Open Edit columns on the Board tab. Drag statuses between columns, drag a column by its ⠿ handle to change the order, rename a column inline, add or remove columns. Open issues in any status you leave in Unmapped statuses are collected into an Unmapped column on the board, so open work never quietly vanishes. Finished issues stay off the board either way.
Three per-column settings live in that editor:
| Setting | Effect |
|---|---|
| WIP limit | An optional whole number ≥ 1. Leave blank for no limit. |
| SLA days | The time limit for a card sitting in this column, in whole days. The input hints at 0.5 steps, but nothing enforces that and ages are floored to whole days everywhere, so a fraction behaves as the next whole day up. |
| Warn at | An earlier warning threshold. Only appears once an SLA limit is set; clearing the limit clears it too. |
WIP limits also appear in Settings. SLA thresholds do not — the Board tab's column editor is the only place to set them. See SLA tracking.
Column headers show the issue count, the story-point sum, WIP state, and how many cards are breaching or approaching their SLA. Done-category cards are left out of the SLA counts.
Click a column header's collapse control to squeeze it to a narrow strip. Collapsed columns are remembered for you, per board.
The toolbar and the column names stay at the top of the page while you scroll, so the column names are in view in every lane.
WIP limits: soft or hard
Each limit has a mode.
- Soft (the default) — the drop goes through and a warning banner appears.
- Hard — the drop is refused before anything is written to Jira, and a dialog explains why.
Cards
Drag a card to another column and Kanban+ transitions the issue in Jira. With no grouping, the whole column is the drop area, header and empty space included, and every column stretches to the height of the tallest. With Group by on, the drop area is the column's cell in each lane, not the shared header above them. The Unmapped column takes no drops. The card moves immediately and reconciles against the server response, so a failed transition snaps back rather than lying to you. Dropping a card on another card in the same column ranks it above that card in Jira. The board only keeps showing that order with Sort set to Rank; under any other sort the card returns to its sorted place at the next refresh.
What's on a card
Choose the fields yourself in Settings → Card fields — the list is your site's actual field catalogue, custom fields included. New boards show assignee, priority, due date and labels.
On top of your chosen fields, a card can carry:
| Marker | Meaning |
|---|---|
| Aging dot and tint | How long the card has sat where it is. Tiers default to 3 / 7 / 14 days and are configurable in Settings → Card Aging. |
🕐 SLA +Nd | The card is past its column's SLA limit by N days. |
⏰ Nd left | The card is inside the warning window, N days from breach. |
| Due-date chip | Shown only when the due date is within 7 days or already past. |
🚫 Blocked | At least one open blocker. |
⚡ Blocking | This issue is holding up others. |
🚩 Flagged | Jira's impediment flag. Hover the card and use the 🚩 button, labelled Flag or Remove flag, to toggle it. |
Card age is measured from the moment the issue entered its current status when Kanban+ has that timestamp, and falls back to the issue's last-updated time when it doesn't. SLA tracking explains where that timestamp comes from and how to backfill it.
Hover a card for quick edits to assignee, priority, story points and the flag. Click it to open the issue in Jira's own issue view, in a popup over the board. Closing the popup refreshes the board.
List, Backlog, Calendar, Delivery Plan and the Dependency Map open an issue the same way. Where Jira can't open the popup, those views and the board open a side panel instead, with inline editing, transitions, comments, links and sub-tasks. The Timeline and Roadmap open the issue in Jira.
On the Board, a sub-task's card also leads to its parent. After its own key and type the card shows the parent's key, as in ABC-14 Sub-task ↑ ABC-12. Click the parent's key on the card to open the parent in the same popup, and hover over it to see the parent's summary. Opening a parent this way doesn't add it to the board. In Select mode the key is plain text, and a click selects the card.
Only a sub-task's card has this link, and only on the Board. An issue under an epic shows the epic's name at the top of its card, and that label is not a link.
For a sub-task, go through the card, because at the moment Jira's popup may not do it. When an app opens the popup, a click on the parent shown at the popup's top left may do nothing. That is a known Jira fault (JRACLOUD-95802), and it covers the other issue links inside the popup too: Atlassian's report says sub-tasks and linked issues clicked there open behind the popup. An app can't change anything inside Jira's popup.
Card colour rules
Settings → Card Color Rules holds an ordered list. Each rule is a field, an operator, a value and one of seven colours; the first rule that matches paints the card.
| Field | Operators |
|---|---|
priority | is, is not |
type | is, is not |
label | contains, is not |
assignee | is, is not (an empty value or unassigned matches unassigned issues) |
Colours available: red, orange, yellow, green, blue, purple, grey. Matching is case-insensitive. Rules are evaluated in the browser, so they cost no extra Jira calls.
Swimlanes
Use Group by in the toolbar to divide the board into horizontal lanes by assignee, priority or epic — or leave grouping off. Assignee gives each person their own row.
Your choice is remembered for you, per board, in any browser, so you don't need to be a board administrator to divide the board. An administrator's choice also becomes the board's default for people who haven't picked one.
Assignee and epic lanes sort by name, and priority lanes follow your site's own priority order. Issues with no value collect in a last lane called Unassigned, No priority or No epic. Each lane shows its card count and collapses on its own (that part is per-person and not saved).
Epic grouping reads the issue's parent, which works in both team-managed and company-managed projects without an extra API call. Epics are recognised by their level in Jira's issue hierarchy, not by name, so a renamed or translated epic type still counts. A sub-task joins its story's epic lane when the story is on the board.
Finding things
Search. Press / or Ctrl/⌘ + F. Matches on key, summary, assignee, priority, type, status and labels.
Quick chips. 👤 Me, ⭕ Unassigned, ⚠ Overdue, 🔴 High+, 🚩 Flagged, 🚫 Blocked. They combine with AND. Me and Unassigned cancel each other out, as you'd expect.
Sprint selector. Lists sprints when Sprint is one of the board's card fields, and then picks up the active sprint automatically on first load.
Sort. Orders the cards inside each column by last updated, priority, due date, created date or rank. Your choice is remembered for you, per board.
Field filters. A Jira-style pill bar for type, status, assignee, priority and epic, with value suggestions from your site. + More filters adds a pill for any other field Jira offers value suggestions for. These compile into JQL and are sent to Jira. The Board and Timeline keep separate sets. The Epic pill lists up to 100 open epics in the board's scope, newest first, and shows the issues directly under the ones you pick. Typing in it searches those 100 only.
Team filter. Teams are people groups shared across every board — create them from the Teams button in the header. Board administrators and site admins can edit them; anyone can use them to filter.
Advanced filter. A clause builder that runs entirely in the browser, on issues the board has already loaded. It never re-queries Jira.
| Field | Operators |
|---|---|
| Text | contains |
| Assignee | is, is not, is empty |
| Priority | is, is not |
| Type | is, is not |
| Status | is, is not, contains |
| Label | contains, does not contain |
| Story Points | =, >, <, >=, <= |
| Due Date | before, after, is empty |
| Blocked | is true, is false |
Clauses join with a single global AND or OR. Two things to know: story points are read from customfield_10016, customfield_10028 or story_points, and an issue with no numeric value is excluded by any story-points clause; and an unrecognised field or operator passes rather than hides, so a filter degrades toward showing more, never less.
Saved views. Name the way the board looks now and it becomes a one-click preset. A view keeps the grouping, sort, sprint, search text, assignee selection, field filters (including pills you added and left empty), quick filters and advanced filter. Board administrators create and delete views, up to 50 per board; a 51st isn't saved, and the board shows no message when that happens. Everyone on the board can apply them. Applying one changes only your own board and isn't remembered: most of it resets when you leave the Board tab, and the field filters and board quick filters when you next load the page. A view never stores an issue summary, so an Epic filter in a view shows the epic's key. A view saved before 2 November 2026 holds only its grouping, assignees and search text, so delete it and save it again to capture the rest.
Your setup is remembered. The board comes back the way you left it, in any browser: grouping, sort, sprint, filters, quick filters, advanced filter, selected assignees and collapsed columns. The search text isn't kept.
Editing several issues at once
Switch on select mode, tick the cards you want, and a sticky bar appears at the bottom. From there you can:
- assign (or unassign)
- set priority
- add a label
- move to a column
- add to a sprint
- export the selection to CSV
Each issue is written individually, so a partial failure leaves the successes in place and reports the rest. Every bulk run produces a before/after diff, which powers a one-click undo.
Creating issues
Each column has a quick-create form: project, issue type, assignee, priority, labels and epic. Press C anywhere in the app for the full create dialog instead.
Issue templates (Settings) turn common shapes into one-click chips above the quick-create form. A template pre-fills priority, labels and an optional summary prefix. Limits: 30 templates per board, names up to 50 characters, up to 10 labels, summary prefix up to 200 characters, and priority chosen from your site's own list.
Done transition guard
Moving a blocked issue into a Done-category column is the classic silent mistake. The guard is set per board, in Settings:
| Mode | Behaviour |
|---|---|
off | Nothing happens. |
warn | The move goes through, and you're told the issue still has open blockers. This is the default for new boards. |
hard | The move is stopped and a dialog explains which blockers are still open. |
The guard looks at direct open blockers only. It runs when you drag a card on the board, like WIP limits and column_enter rules. A bulk move, or a status change in Jira's popup or the side panel, skips all three.
Board Insights
✨ Insights in the toolbar opens a panel that scores the board 0–100 and lists what's dragging it down — WIP breaches, SLA violations, blockers, overdue issues, stale work in progress. Each insight expands to the affected issues. There's a question box that keyword-matches against the board data.
This runs entirely in your browser, on data the board already loaded, plus a search of your own Jira, made as you, for up to 1,000 finished issues updated in the last 30 days. That search runs when you open the panel, or when the board loads if it lists sprints, and again if the filters change. It makes no other network calls, and there is no model behind it — it is arithmetic and keyword matching, not AI.
Export
Export CSV writes the currently visible cards, or only the selected ones from the bulk bar. Columns: Key, Summary, Type, Status, Column, Priority, Assignee, Reporter, Labels, Story Points, Due Date, Is Blocked, Blockers, Days in Column. The file carries a UTF-8 byte-order mark so Excel opens it correctly.
The Timeline
The Timeline draws the same board scope as a Gantt chart, windowed to updated >= -90d. View modes are Day, Week and Month.
Where the bars come from
Bars are drawn from Jira's Due date and a Start date custom field, which Kanban+ discovers on your site. Where a date is missing, it fills in:
| Situation | Bar |
|---|---|
| Start only | Start to start + 3 days |
| Due date only | Due date − 3 days to due date |
| Neither | Today to today + 2 days |
If your site has no start-date field at all, a banner says so: bars are drawn from the due date, and dragging saves only the due date.
Drag a bar to reschedule. It snaps to whole days and writes back to the Jira issue immediately.
Dependencies on the timeline
The Deps button draws arrows between issues linked with Jira's Blocks link type. Arrows appear only when both ends are in the currently loaded issue set.
- Blue arrow — a healthy dependency.
- Red arrow — a scheduling conflict: the blocker ends after the blocked issue is due to start. A banner lists the first few.
- Amber bar border and an amber dot in the task list — the issue sits on the critical path, computed from your real Jira dates.
One precise limitation: the Timeline matches the link type named exactly Blocks. If your site renamed it, the arrows go quiet even though the board's blocked badges and the Dependency Map still work, because those match any link type containing "block".
Board administrators can also set a per-issue bar colour, and add a blocker by typing an issue key — which creates a real Jira "Blocks" link, not a Kanban+-only annotation.
Clicking a row in the left task list opens the issue in Jira through the host's own navigation.
The other views
| View | What it does |
|---|---|
| Summary | Headline counts for the issues in the board's scope updated in the last 90 days, finished ones included. |
| Backlog | Sprint and backlog management: create a sprint, start and complete one, move issues between sprint and backlog. |
| Calendar | Due dates on a month grid. |
| List | A flat, sortable table of the issues in the board's scope updated in the last 90 days, finished ones included. |
| Reports | Active sprint progress, velocity across the last eight closed sprints, and per-assignee workload. Charts are hand-drawn SVG — no chart library, no CDN. |
| Roadmap | Epics and their children over time. |
| Portfolio | Every Kanban+ board on the site in one health table, plus cross-board blockers. See Cross-board dependencies. |
Known limits
- Story-point sums in column headers and on cards read
customfield_10016. A site using a different field id loses those numbers (the advanced filter tries three ids and is more forgiving). - The impediment flag assumes
customfield_10021with option id10019— the Jira Cloud defaults. Non-default sites won't flag correctly. - Timeline dependency arrows need the link type to be named exactly
Blocks. - Timeline bars need a start-date field on the site to show real durations.
- Board configuration is saved with a revision check, but Forge storage has no compare-and-set, so two administrators saving the same board within the same second can still overwrite one another. Single-field saves skip the check entirely.