The operator has no single place showing what needs attention #78

Open
opened 2026-09-21 07:18:24 +00:00 by cgalo5758 · 4 comments
Owner

What a person cannot do today

See, on the landing page, everything that is stuck or unfinished. The page now carries the daily numbers and one card per system, each reporting its own state; work that has failed, a provider that was never configured, a setup that was never finished and an invoice that is overdue are found by visiting four different pages.

What they should be able to do

Read one section that collects them: work that failed past its retries, a provider that published products depend on but that is not configured, an incomplete setup, and overdue invoices, each line linking to the page where it is fixed. With nothing in it the section says so in plain positive words rather than reporting zero findings.

Why it matters

The landing page is where an operator starts the day, and its job is to say whether anything is wrong. Without an aggregator the answer is spread across the pages an operator would only visit if they already suspected something.

Where

The operator overview handler and its template.

Done when

One section on the overview lists every outstanding item of those kinds with a link each, its empty state reads as all clear, and a new kind of attention item is added by registering it rather than by editing the template.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today See, on the landing page, everything that is stuck or unfinished. The page now carries the daily numbers and one card per system, each reporting its own state; work that has failed, a provider that was never configured, a setup that was never finished and an invoice that is overdue are found by visiting four different pages. ## What they should be able to do Read one section that collects them: work that failed past its retries, a provider that published products depend on but that is not configured, an incomplete setup, and overdue invoices, each line linking to the page where it is fixed. With nothing in it the section says so in plain positive words rather than reporting zero findings. ## Why it matters The landing page is where an operator starts the day, and its job is to say whether anything is wrong. Without an aggregator the answer is spread across the pages an operator would only visit if they already suspected something. ## Where The operator overview handler and its template. ## Done when One section on the overview lists every outstanding item of those kinds with a link each, its empty state reads as all clear, and a new kind of attention item is added by registering it rather than by editing the template. Migrated from status/issues.md at b7a0e15
cgalo5758 added the
kind
enhancement
area/operator-ui
labels 2026-09-21 07:18:24 +00:00
Author
Owner

Related: #168 (notifications). A notification about a condition listed here links to its line; reading the notification does not clear the line, fixing the condition does.

Related: #168 (notifications). A notification about a condition listed here links to its line; reading the notification does not clear the line, fixing the condition does.
Author
Owner

Changes to an org type's default plan or to a ladder's tier order record every organization they still have to move (#187). The ones that could not be moved are listed on the org type's card or the ladder's page, next to a Retry button. That gives this overview one kind of item: "organizations a plan change could not move", with its line linking to that card or page. A page for each change, listing every organization it reached and how each one ended, would be a better place for that line to link to, and the records #187 keeps are enough to build it.

Changes to an org type's default plan or to a ladder's tier order record every organization they still have to move (#187). The ones that could not be moved are listed on the org type's card or the ladder's page, next to a Retry button. That gives this overview one kind of item: "organizations a plan change could not move", with its line linking to that card or page. A page for each change, listing every organization it reached and how each one ended, would be a better place for that line to link to, and the records #187 keeps are enough to build it.
Author
Owner

The operator overview's setup banner is closed today through an instance setting, setup_banner_dismissed in core.instance_settings (declared in internal/instance/settings.go). An incomplete setup is one of this section's kinds. Once the section exists, the setup is a line here that clears when the setup is finished, and the banner and its setting can go.

The notice part (#167) keeps no record of closed notices and gives a condition that stays wrong until someone fixes it no close button: fixing it is what clears it.

The operator overview's setup banner is closed today through an instance setting, `setup_banner_dismissed` in `core.instance_settings` (declared in `internal/instance/settings.go`). An incomplete setup is one of this section's kinds. Once the section exists, the setup is a line here that clears when the setup is finished, and the banner and its setting can go. The notice part (#167) keeps no record of closed notices and gives a condition that stays wrong until someone fixes it no close button: fixing it is what clears it.
Author
Owner

Toasts are another way the console tells a person something: the error toast when a request fails and the success toast after an action (internal/embeds/static/error-handler.js, internal/embeds/static/success-toast.js). This section has to decide its relation to them along with notifications (#168). For example, does an item that becomes outstanding while the operator is on a page announce itself with a toast, or only appear here?

Toasts are another way the console tells a person something: the error toast when a request fails and the success toast after an action (`internal/embeds/static/error-handler.js`, `internal/embeds/static/success-toast.js`). This section has to decide its relation to them along with notifications (#168). For example, does an item that becomes outstanding while the operator is on a page announce itself with a toast, or only appear here?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#78