fix: map kanban priority labels in headers #1414
Closed
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.
fix-prio-label-mapping
Kanban Priority Label Mapping
This change ensures Kanban column headers use the configured priority labels when grouped by priority (including swimlanes), instead of the raw stored values.
Examples (illustrative):
highwith label "High Priority" renders as "High Priority" in the column header.Changelog
cf. PR.md