Priority Board for Jira – User Guide and Setup
How to use Priority Board for Jira: set priorities by drag and drop, rank inside a priority, bulk-move with undo, swimlanes, shared views, sprints and gadget.
Priority Board shows a project’s issues by priority: Highest, High, Medium, Low. Drag a card to another column to change its priority, score issues with RICE, WSJF or ICE, and plan sprints from the top of the list.
How to read the pictures. Every screenshot comes from a real Jira site. The red boxes with numbers show where to look or click. Number 1 in the picture is step 1 in the text, number 2 is step 2, and so on.
Get started in 2 minutes
- Install Priority Board from the Atlassian Marketplace (a Jira admin; free for up to 10 users).
- Open it: a project’s sidebar → Priority Board.
- Drag a card to another priority column — the issue’s real Priority changes in Jira. Issues without a priority wait in the last column, No priority.
- Save changes keeps the board as your saved view; Filters → Projects or Groups widens it to the whole team.
Overview
Priority Board shows one Jira project’s issues in one column per priority of the project’s priority scheme — Highest, High, Medium, Low and Lowest on most sites. Dropping a card on another column sets the issue’s real Priority field. Inside a column the cards stand in Jira’s rank order, the same order your Jira boards and backlog show.
Every change is made as you, with your own Jira permissions: if you cannot edit an issue in Jira, the app cannot either — the card goes back and a message gives Jira’s reason. The app runs on Atlassian Forge and stores only your saved filters and views, and the scores you save on issues, in your Atlassian site.
Priority Board uses Jira’s own Priority field. A project can also score its cards with RICE, WSJF or ICE: see Scores: RICE, WSJF, ICE.
Install and open the board
- Install Priority Board from the Atlassian Marketplace (a Jira admin approves the permissions).
- Open a project. Priority Board is in the project’s navigation, next to Summary, Backlog and Active sprints (under More when the row is full).

- Open a project and click Priority Board in its navigation (under More when the row is full).
The board shows that project only. You need the “Browse projects” permission in it.
The priority board
Each column has the priority’s icon, name and number of issues. Issues without a priority are not shown. Done issues show no due marks.

- The view tabs: By priority, Sprints; + adds more.
- Click a person to see only their issues; Mine shows yours.
- Filters narrows the board.
- Each column is a priority, with the number of issues. Drag a card to another column to change its priority.
- With scoring on, every card shows its score, for example RICE 3600.
- Change the priority: drag a card to another column, or open its ⋯ menu and choose a priority under Move to.
- Rank inside a priority (Jira Software sites): drag a card up or down in its column, or use Move up / Move down in its menu. The new place is stored as the issue’s rank in Jira, so the backlog and Jira’s boards show the same order.
- If the Priority field is not on the issue’s edit screen, Jira refuses and the message says so — add Priority to the screen in Project settings → Issue types.
Reprioritize several issues at once
Ctrl+click (⌘+click or Shift+click) cards, or choose Select in a card’s menu. The bar “N selected” offers Move to… and Clear selection (also Escape).
- Point at a card and click ⋯.
- Select adds it to a group move; View the issue and Edit summary work on this card.
- Rank: move it up or down in its column.
Each issue is changed like a single move: one that Jira refuses goes back with the reason, the others move. The message “N issues moved to …” has Undo for all of them, and Ctrl+Z (⌘Z) does the same. Only the last move can be undone.
Edit from the card
Click the assignee avatar to choose another person who can be assigned in the project, or Unassigned. Edit summary renames the issue (Enter saves, Escape cancels). View the issue opens Jira’s issue dialog.
Issues without a priority
When the project has issues with no priority, a last column No priority appears and lists them. Drag a card out of it to give the issue that priority; no card can be dropped into it, and the column disappears once it is empty.
Scores: RICE, WSJF, ICE
Priority Board can score every issue with one framework per project. It is off by default, so the board stays as it was until someone turns it on.
-
Click Score on a card (or its score, such as RICE 720).
-
The formula is at the top.
-
Fill in the inputs, here Reach; the score updates as you type.
-
Press Save.
-
Open View settings → Scoring and pick RICE, WSJF or ICE. A project admin or a Jira admin can change it; others see the choice.
-
Every card now shows its score (RICE 266.7) or Score if it has none. Click it.
-
Fill in the inputs. The formula is at the top and the score updates as you type:
- RICE — Reach (people or events per quarter), Impact (3 massive, 2 high, 1 medium, 0.5 low, 0.25 minimal), Confidence % (0 to 100), Effort (more than 0). Reach × Impact × Confidence ÷ Effort.
- WSJF — Business value, Time criticality, Risk reduction and Job size, each 1, 2, 3, 5, 8, 13 or 20. (Value + Time + Risk) ÷ Job size.
- ICE — Impact, Confidence and Ease, each 1 to 10. Impact × Confidence × Ease.
-
Save. Values out of range are refused with a message next to the field (for example “Effort must be more than 0.”) and Save stays off.
Find scored issues with JQL. The score is saved on the issue (issue property simplify-priority-score), so Jira search can use it: project = PAY AND priorityScore > 20 ORDER BY created DESC.
Sort by score. View settings → Sort cards by score lists each column highest first and unscored issues last. It is saved with the view and does not change Jira’s rank.
Without permission to edit an issue you see its inputs read-only.
Triage with swimlanes and due marks
Board settings (the gear next to Refresh) splits the board into swimlanes — by Assignee, Parent (epic), Priority or Project. Here the board is split by epic:
Columns keep one order in every lane, a card moves within its lane, and a lane folds when you click its title. The other settings:
- Column sums — issue count only, original or remaining estimate, Story Points or another number field (Σ in each column header).
- Card fields — Parent, Status, Due date, Labels, Components, Fix versions or Remaining estimate on every card.
- Auto-refresh — off, or every 1, 5, 15 or 30 minutes while the page is open.
Cards are marked Overdue (red), Due today, Due tomorrow or Due in N days (up to 3, amber) — hover a mark to see the date.
A column’s ⋯ menu moves it left or right and sets a WIP limit (1–999): the header shows “cards / limit” and turns red over it, without stopping a move.
Filters and quick find
Only my issues and Assignees are always visible; More filters opens Include statuses, Exclude statuses, Issue types and Created after / before. Clear filters empties them all.
Next to them, Find by key or summary, Mine and Unassigned narrow the cards already on screen at once; they are not saved.
A board loads up to 1,000 issues; if more match, “Not every issue is shown” asks you to narrow the filters.
Profiles
The Profile select keeps named sets of filters, per project. The board opens with default.
- Save stores the filters, the column order, WIP limits and board settings in the selected profile (“Unsaved changes” shows until you do).
- To create a profile, type a new name into the select and choose Create profile ”…”.
- ⋯ → Delete profile… removes one, after you confirm.
Profiles are yours; nobody else sees them.
More boards as view tabs
The first tab, By priority, is the board above. + (Add a view) adds other boards to this project page: By due date, By status, By assignee, Workload, Sprints and By field… (Labels, Components, Fix versions or a single-select field).
Plan sprints from priorities
The Sprints view (Jira Software) shows a Scrum board’s Backlog, the active sprint and the future sprints. Drop a prioritized issue on a sprint to move it there, or on Backlog to take it out of its sprint — in Jira, as you.

- Open the Sprints tab.
- Choose the Scrum board.
- Drag cards from Backlog into a sprint column. Each column shows its dates and how many days are left.
Boards by component, label or any select field
By field… asks which field to group by. Each value becomes a column, plus None. Dropping a card on another column replaces the value it was shown under; dropping it on None removes that value.
Share and link views
With an added tab selected, the ⋯ menu next to Save renames, moves or removes it, and Share with the project shares it as it is now. Everyone who can open the project page finds it under + → Shared views. The person who shared it and project admins can save changes for everyone; anyone else can Save as my view. The page address follows the selected tab, so you can send a link to a view.
Export to CSV
⋯ → Export to CSV saves the cards on screen (quick filters apply) as a spreadsheet with key, summary, column, status, priority, assignee and due date. The file is made in your browser.
Dashboard gadget
Add Priority Board to a Jira dashboard (Edit → Add gadget). In its Configure, choose the board, the Project, the column sums and how often it refreshes. The gadget lists issues per priority with a bar for each column’s share:
It searches Jira as the person looking at the dashboard, so everyone sees only the issues they may see.
Keyboard
The cards are one Tab stop: ↑ / ↓ within a column, ← / → to the next column with issues, Home / End and Ctrl+Home / Ctrl+End to the first and last issue; Enter or Space opens the card’s menu. Columns also have Move left / Move right in their menu.
Saved views, Mine and View settings
Since the November 2026 redesign every board has the same frame:
- Column sums: issue count or a total under each column.
- Card fields: click a field to show it on every card.
- The preview shows how a card will look.
- WIP limits per column.
- The saved view next to the app’s name (”· default ▾”): switch views, Save as new view…, Rename, Delete view… and share a view with the project or everyone. While the board differs from what is saved, Save changes and Discard appear.
- Quick filters next to Filters: Find issues, Mine and Unassigned.
- View settings — a panel beside the board: Group by (swimlanes), Column sums, Card fields with a live preview, WIP limits of every column in one list, and Auto-refresh. Every change shows at once and is kept with Save changes.
Permissions and data
- Issues stay in Jira. The app changes them through Jira’s REST API as you; every change is in the issue history.
- Stored by the app: your profiles, view tabs and shared views, and the project’s scoring framework, in the app’s Forge storage inside your Atlassian site. Nothing is sent outside Atlassian.
- Scores are saved on the issue as the issue property
simplify-priority-score, with your permissions. Anyone who can see the issue can see its score; JQL can search it aspriorityScore. Uninstalling the app leaves the property on the issues. - Permissions: read and write Jira work, read users and groups, app storage, Jira configuration (to list group members), and — for ranking and the Sprints view — Jira Software’s board, sprint and rank permissions. Without Jira Software, everything except ranking and Sprints works.
- On uninstall the saved profiles and views are removed; your priority changes stay in Jira.
See the privacy policy.
Troubleshooting
- An issue is missing — it has no priority, a filter hides it (Clear filters), or more than 1,000 issues match.
- A priority change fails — the Priority field is not on that issue type’s edit screen.
- The order inside a column does not stick — ranking needs Jira Software, and your permission to rank in the project.
- “Issues could not be loaded: …” — press Retry. “Profiles could not be loaded” — press Try again; nothing is lost.
- Dark mode — the board follows Jira’s theme.
Still stuck? Contact support.
Related apps
- Kanban Status Board — the same board by workflow status, with real transitions.
- Deadline Tracker — every deadline across projects, rescheduled by drag and drop.
- Workload & Capacity Planner — who has too much, by week, against capacity.