Ticket Board

On the [Events & Alerts > Ticket Board] page, you can track and work through every issue in your organization in one place — whether it came from a Well-Architected assessment, an external alert, or was raised by hand.

Page Layout

KPI cards

Every card is clickable — selecting one filters the list to exactly those tickets.

Ticket List

Toolbar

Filtering by period

Three independent time axes narrow the board, each with its own tab in the filter:

Each axis offers All time, Last 3 days, Last 7 days, Last 14 days, and Last 30 days — the last one covers “tickets raised this month”. The axes combine, so you can ask for tickets created in the last 30 days that were also updated in the last 3. A tab whose axis is set shows a count, and [Reset filters] clears all three along with the rest.

Column pinning

Open ⋮ > Set Display to change rows per page, hide or reorder columns, and pin up to 2 columns to the left so they stay visible while you scroll the wide table horizontally. The layout is kept in your browser. Narrowing the list — a new search, filter, or KPI card — always returns you to page 1.

Exporting tickets

Export in the toolbar opens a dialog that builds a file from the tickets matching the current filters, with the columns that are visible on screen in the same order. The board keeps years of history, so the dialog opens with Last 90 days already applied and shows how many rows that is against the limit — Excel up to 30,000 rows, CSV up to 50,000.

Kanban view

Switching to kanban groups tickets into a lane per status and lets you drag a ticket from one lane to another to change its status. Transitions that are not allowed are refused with an explanation rather than silently reverting.

Each lane shows its own count in the header and loads more cards as you scroll it, so a lane holding tens of thousands of tickets stays usable. The KPI cards above are clickable too — selecting one filters the board to exactly those tickets, in either view.

Changing status

Click the chevron next to a ticket’s status to see which transitions are available from where it is now — for example an Open ticket offers Start Progress and Dismiss. Only valid next states are listed.

Ticket Detail

Click a ticket to open the preview panel beside the list. [View full ticket] opens it as a full page.

Re-collecting the resource

At the bottom of Resource Info, Last collected shows when the affected resource was last read from the cloud provider, with a [Re-collect] button beside it. This is the shortcut for the common case: you fixed something in the CSP console and want the ticket to catch up, without leaving for the resource inventory to find that one resource.

Once the request is accepted the row reports where the collection stands:

The state shown is what the server reports for the resource, so it stays accurate even if you reload or come back later. If the collection resolves what the ticket was raised for, the ticket is reconciled and closes on its own; the detail refreshes so you see that here rather than having to reload.

[Re-collect] is never locked while a collection is running — pressing it again is simply refused with Re-collection is already in progress, which is not an error.

Creating a Ticket

The panel on the right tracks progress through the three steps, so you can see what is still outstanding before saving.