Show parent-link children in Sub tab on Cloud#66
Merged
textfuel merged 5 commits intotextfuel:mainfrom May 3, 2026
Merged
Conversation
textfuel
requested changes
May 3, 2026
Owner
textfuel
left a comment
textfuel
left a comment
There was a problem hiding this comment.
Thanks for the PR!
Cloud/DC split is clean and the test coverage is great.
Left two comments inline. One looks like a real bug worth a test, the other is more of a UX question.
Overall really like the direction
seflue
force-pushed
the
feat/parent-link-children
branch
from
9cf729c to
30b8753
Compare
The active tab (Info/Lnk/Sub) now persists across issue changes, so navigating between tickets keeps users on the tab they chose. Cursor and offset still reset, since they reference issue-specific positions that no longer apply to the new issue.
The Sub tab now lists children fetched via JQL "parent = KEY" on Cloud, alongside classic subtasks on Server/DC. Cloud uses the parent-link model where children are not exposed via Issue.Subtasks, so the info panel issues a dedicated fetch when a parent issue is selected. Responses are tagged with an epoch counter so stale results from rapid selection changes are dropped, mirroring the existing preview-debounce mechanism.
seflue
force-pushed
the
feat/parent-link-children
branch
from
30b8753 to
4e49738
Compare
seflue
force-pushed
the
feat/parent-link-children
branch
from
4e49738 to
8348d42
Compare
textfuel
approved these changes
May 3, 2026
Owner
textfuel
left a comment
textfuel
left a comment
There was a problem hiding this comment.
Thanks for the fix and the tests, looks good now
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.
Closes #65
On Cloud, the Sub tab is now sourced from
parent = <KEY>instead of
Issue.Subtasks. Epics show their Stories (and anyother parent-link children that don't surface as classic
subtasks). Stories with subtasks render the same as before. DC
is untouched:
GetChildrenis a no-op there and the tab keepsreading
Issue.Subtasks. The DC equivalent ("Epic Link" = KEY)is left for a follow-up since I can't test it.
Two changes that ride along:
user has configured in their Jira instance (Story, Bug, ...),
so the bare key isn't enough to tell what you're looking at.
skim through Epics with the Sub tab open to scan their
children.
Notes:
App.childrenEpochmirrors the existingpreviewEpochpatternfor dropping stale responses on rapid selection.
InfoPanel.MaybeChildrenRequestis the gating: fetch only whenSub is active and the current key is neither loaded nor errored.
prefetched after the list arrives so Enter is instant.