Repository navigation
List a system's remediation actions worst criterion first - #44
Merged
Merged
Conversation
The system page showed remediation blocks in fixed criterion order, so a critical Security block could sit below a green one. It now uses the same severity band then score ordering the overview card already picks its one action by, shared as rankedActions in criteria.js. Criteria with actions but no score go last. Co-Authored-By: Claude Opus 5.5 <[email protected]>
maciej-szlosarczyk
approved these changes
Oct 16, 2026
joshsiaw
added a commit
that referenced
this pull request
Oct 27, 2026
The system page showed remediation blocks in fixed criterion order, so a critical Security block could sit below a green one. It now uses the same severity band then score ordering the overview card already picks its one action by, shared as rankedActions in criteria.js. Criteria with actions but no score go last. Co-authored-by: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The system page listed remediation blocks in fixed criterion order, so a critical Security block could appear below a green one.
It now orders them the way the overview card already picks its single action: severity band first (critical, high, medium, low), then score within the band. Criteria that carry actions but have no score go last. The ordering lives once, as
rankedActionsincriteria.js, andtopActionnow uses it too.Checked in Chrome against a real board: the branch lists a capped system's Security block first, while
mainlists it last.🤖 Generated with Claude Code