Getting started

Old Skool Board is an extension of a Jira Software board — there is no need to create new boards from scratch. When you open it, it reads the configuration of whichever board you're currently viewing — columns, statuses, and board type (Kanban or Scrum) — and mirrors that setup automatically.

It picks up where your board leaves off.

• Jira Software board — designed to work with existing Scrum or Kanban boards; other board types are not supported
• Jira Cloud — Server and Data Center are not supported
• Desktop browser — mobile and tablet are not supported
• Parent items with sub-tasks — the board's value comes from that relationship; it has limited use for flat issue structures

Old Skool Board maps your work items to one of three columns — To Do, In Progress, and Done — using Jira's status category system. Sub-tasks use their actual Jira status, appearing as lanes inside the In Progress workspace.

This means the board will work with any workflow structure you already have.

That said, we've found it works best when:

• Work items have three statuses — one mapped to each category: To Do, In Progress, and Done
• Sub-tasks have their own dedicated workflow, separate from work items

When work items are kept simple and sub-tasks carry the detail, the In Progress workspace becomes a genuinely useful view of what's actually happening inside each item. But how you structure your Jira project is entirely up to you.

Find Old Skool Board on the Atlassian Marketplace and install it to your Jira Cloud site. Once installed, it appears as a page inside your Jira projects.

Navigate to a Jira project and click More in the top navigation bar. In the dropdown, select Old Skool Board to open the board.

Click the settings icon in the top-right corner of the board to open the Board settings panel. From here you can:

• To Do / In Progress / Done status — map your project's workflow statuses to the three board columns
• Done retention (Kanban only) — control how long completed items remain visible before being archived

Settings are saved per-project.