Repository navigation
feat(frontend): implement shared list-column configuration for list and tree views - #324
Merged
stefan-ernst merged 1 commit intoOct 12, 2026
Conversation
danielraab
changed the title
This was referenced Oct 12, 2026
Contributor
|
Thank you @danielraab - merging this in |
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
2 participants
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.
Configurable fields in the tree view
The list view lets you pick which fields are shown; the tree view had a fixed set (key, summary, status, priority, created).
The tree now has the same field selector and uses the same column configuration as the list view.