What Old Skool Board can do

• Your Jira board's own columns — same names, same order, including columns that hold several statuses
• Expand a column to see its sub-task lanes — your board's own columns that hold sub-task statuses, in the same order
• Collapse the expanded column — at most one column is open, and you can close them all
• Split-pane layout in the expanded column — fixed parent item panel with scrollable sub-task lanes
• Unmapped work items shown below the board, so a work item whose status has no column is never silently lost
• A sub-task whose status isn't in any column isn't shown on the board, as on Jira's own board. It stays listed in its parent item's details
• Epic chips on cards, colour-coded to match Jira
• Issue type icons on every card
• Done retention on company-managed Kanban boards — hide completed items not updated in 1, 2, or 4 weeks

Click any card title to open its full details without leaving the board.

• Rich text description editing with bold, italic, underline, links, and lists (powered by TipTap)
• @mentions — type @ to search and mention teammates
• Comments — read, add, and reply
• Linked work items and sub-tasks, with drill-in navigation
• Detail sidebar — edit assignee, priority, labels, status, due date, and start date
• Change issue type from the card or its details
• Inline title editing
• Open in Jira — Cmd/Ctrl-click a card, or click the key in the work item details

• Drag a parent item to choose its status and its position in one gesture — a column with several statuses shows a box per status, then an insertion line for exact placement
• Parent item order is saved to Jira's native rank — reorder in Old Skool Board or in Jira, and each shows the same order when it loads
• Drag a sub-task within its parent item's row to choose its status and position the same way — a lane with several statuses shows a box per status, then an insertion line (see Known limitations for dragging quirks)
• Sub-task order is also saved to Jira's native rank, so Old Skool Board and Jira show the same sub-task order when they load
• One sub-task move per parent item at a time — other rows and parent items stay free
• Reordering parent items needs a board filter ordered by Rank and Jira's Schedule work items and Edit work items permissions. Without them, reordering is switched off and the board tells you why when you try, instead of silently undoing the drop. You can still change status
• Reordering sub-tasks needs the same Jira permissions, but not a board filter ordered by Rank. If Jira refuses, sub-task order is read-only until the board reloads. You can still change status

• Text search across the board
• Filter by issue type or label (multi-select)
• Quick filters — toggle pills that match your Jira board's quick filter definitions
• Type, label, and quick-filter selections are remembered per board, for your account (text search isn't)

• Inline creation for parent items and sub-tasks — add work without leaving the board
• Choose the status when creating in a column or sub-task lane that holds several statuses
• Choose issue type when creating
• New sub-tasks are placed in the status you choose

• Automatically maps to your current Jira board — no setup in the app; sub-tasks appear when their statuses are mapped to a column in Jira
• Settings and filters saved per board, for your account

See also Known limitations.

• Jira Software board, Scrum or Kanban
• Jira Cloud (Server and Data Center are not supported)
• Desktop browser (mobile and tablet are not supported)
• Works best with parent items that have sub-tasks — limited value for work items without sub-tasks
• Reordering parent items needs a board filter ordered by Rank and Jira's Schedule work items and Edit work items permissions. Reordering sub-tasks needs the same Jira permissions, but not a board filter ordered by Rank
• Active Marketplace license required