Repository navigation
feat(frontend): add configurable fields to backlog rows - #490
Merged
stefan-ernst merged 1 commit intoNov 12, 2026
Merged
Conversation
Contributor
Author
mijelsma
marked this pull request as draft
November 12, 2026 11:19
mijelsma
marked this pull request as ready for review
November 12, 2026 11:25
stefan-ernst
added a commit
that referenced
this pull request
Nov 12, 2026
feat(frontend): add configurable fields to backlog rows
Contributor
|
Great, merging this in to ship with 0.9.5 - I will consolidate the other configurable parent fields to work the same way so we have a consistent behavior across views |
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.


What this solves
Issue #489 describes how child items in the backlog only show their own key and title. This makes similarly named child items difficult to distinguish because users must open each item to discover its parent.
This PR displays the parent directly beside the child item’s title, including:
Parent information is constrained and truncated on narrow screens, with the full value available as a tooltip. This keeps the child title as the primary content and prevents long parent titles from taking over the row.
Additional improvements
Rather than hard-coding another permanently visible field, this PR adds a Configure Fields menu for backlog rows.
Users can choose to display:
The selected fields are saved per user and backlog scope, including workspace, collection, and global backlogs.
Parent, status, and story points remain enabled by default, so the existing backlog presentation is preserved while adding the parent context requested in #489.
Empty values are not rendered. Long values truncate responsively, and parent information continues to respect workspace permissions.
Why this is useful beyond the original issue
The original issue demonstrates that backlog rows sometimes need more context than only a key and title. Making row metadata configurable solves the immediate parent problem while allowing different teams to choose the information they need without permanently increasing visual clutter for everyone.
It also provides a reusable path for backlog metadata instead of adding every future field as another always-visible element.
Testing
npm run checknpm run check:inline-stylesnpm run typechecknpm run test -- --runnpm run build:appCloses #489