Skip to content

fix(frontend): Jobs, Exceptions and Alerts say what they mean in plain words - #2424

Merged
ExtraToast merged 1 commit into
integration/managementfrom
fix/2385-plain-copy
Oct 13, 2026
Merged

ExtraToast merged 1 commit into
integration/managementfrom
fix/2385-plain-copy

Conversation

@ExtraToast

Copy link
Copy Markdown
Contributor

Part of #2385 (step 6).

What this is

The Jobs, Exceptions and Alerts pages came back from the archive tag with wording that was corrected once before, and with some sentences that are hard to read. This changes the words only.

What changes

Labels that were corrected earlier and had come back:

Was Now
Hide for me Hide
Show again Make visible
Run again Re-run

Other lines:

Page Was Now
Alerts What needs someone, gathered from every page in Management. Each alert clears itself once it is dealt with. Problems that need someone to act. An alert goes away by itself once the problem is fixed.
Alerts What needs a look (column) Alert
Alerts For you, with "Each clears itself once it is dealt with" Open
Alerts Still open, just out of your way Not fixed yet, only hidden for you
Alerts Hidden for you · 2 Hidden · 2
Alerts Nothing needs you right now. No open alerts.
Exceptions Every exception the api did not handle, one row per type and place however often it fired. Errors the api did not handle. The same error from the same place is one row, however often it happened.
One exception What it concerned last Where it last happened
One exception It carried no message. No message.
One exception Mark resolved Mark as resolved
Jobs Work the site does in the background: sends, syncs, reconciles and Discord posts. Tasks the site runs in the background, such as sending email, syncing contacts and posting to Discord.
One job What it concerns Related to
One job Nothing in particular. Nothing.
One job Run although it would have been skipped It ran even though it would have been skipped
Run a job This job takes no arguments. This job needs no input.

Left as they are, because the site says the same elsewhere: "could not be read" and "No such job".

How it was checked

  • No testid changes. The tests that quote a sentence are updated with it.
  • 191 unit tests in the touched areas pass, typecheck and lint are clean.

…n words

Labels that were corrected before come back as corrected: Hide, Make visible
and Re-run. Sentences written as riddles are said plainly: "Problems that need
someone to act", "No message.", "Where it last happened", "Related to" and
"This job needs no input."
@github-actions

github-actions Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Changes

Bucket Files Added Removed
frontend 6 █████ 22 ░░░░░ 22
tests 5 ██ 9 ░░ 9
total 11 +31 −31

0.41 test lines per prod line.

Coverage

Statements Branches Functions Lines
frontend 94.48% 89.93% 92.87% 95.23%
main 08fdcf6 92.74% 88.01% 90.20% 93.37%
Δ +1.74 +1.92 +2.67 +1.86

Patch coverage: this pull request changes no line that coverage measures.

No coverage reached this report for api (api-unit-test-reports).

@ExtraToast
ExtraToast merged commit d7d10b8 into integration/management Oct 13, 2026
34 checks passed
@ExtraToast
ExtraToast deleted the fix/2385-plain-copy branch October 13, 2026 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant