User guide
The CAB workbench
The change agenda: every change record in the project, in the order somebody running a review would want them, with five filters that carry their own counts.
Who this is for: agents — and whoever chairs your change advisory board.
Where to go
Your project → Concessa → CAB workbench.
What it is
Both a record and an agenda. The workbench holds the board’s meetings — when it meets, who was there, what it discussed and what it decided to do — and, below that, the same ordered table of change records this page has always shown. Authority stays exactly where it was: nothing here makes a meeting a precondition for approving a change, and no meeting outcome changes a change’s governance status. Approving is still per-record and delegable, decided in the issue panel (guide 3). What a meeting adds is a place for the board’s own business to be a record too, rather than something recorded nowhere but a diary or a chat thread.
The change agenda
Below the meetings block sits the same table this guide has always described: every change record in the project, in the order a reviewer wants them. Its heading carries the total, so you know the size of the agenda before reading a row.
The ordering
The list is sorted, not filtered, by this priority:
- Changes awaiting your own decision — the ones you are personally holding up.
- Changes in a freeze window — including overridden ones. An override is a recorded decision to proceed into a freeze, which is exactly what a reviewer wants to see rather than have hidden.
- Higher risk first.
- Soonest planned start first. Unscheduled changes come last.
- Issue key, so the order is stable.
A change awaiting you is also labelled — awaiting you in its summary.
The filters
Five chips, each showing its own count across the whole project — so the counts tell you what is there before you select anything. The chip you are on is shown as selected, and a line beneath the table says the same thing in words — “Showing 6 of 40 changes — awaiting me.” — because a filter you cannot see is a filter you forget you set. On All it simply says “Showing all 40 changes.”.
| Filter | Shows |
|---|---|
| All | Every change record in the project. |
| High risk | Changes you marked High. |
| Emergency | Changes of type Emergency. |
| In freeze | Changes in a freeze window — conflicting and overridden. |
| Awaiting me | Changes with an approval request addressed to you and not yet answered. |
Awaiting me is the one to start your day with.
The columns
Change · Summary · Risk · Type · Planned · Approvals · Status. The approvals column is the progress line from guide 3 — “1 of 2 approved”, or “2 of 3 rejected” when somebody has said no.
Summary here is the Jira issue’s own title, not the Summary of the change recorded in the panel (guide 2). The title tells you which change this is; the recorded summary tells you what it does, and you read it on the change itself.
Select a change key to open that change in a new tab. The workbench and the filter you were on stay behind it, so you can work down the agenda without losing your place.
Two empty states
“Nothing is under change governance yet” means no issue in the project has a change record. Open a governed issue and record its change details.
“No changes match this filter. Choose another filter to see more.” means there are records, just none of this kind. The column headings stay put while you try another chip.
What this guide does not cover
Approving anything — that happens in the issue panel (guide 3), which the change key here links to. Setting the CAB schedule and the standing agenda — that is a project administrator’s job, covered in guide 1.