Show parent issue key in issue view - #5
Merged
Merged
Conversation
Fields.Parent was already being parsed from the API response but never surfaced in the issue view banner, so users had no way to see an issue's parent without opening it in the browser.
rethab
added a commit
that referenced
this pull request
Aug 5, 2026
When an issue has a parent, \`jira issue view\` currently gives no indication of it — you'd have to open the issue in the browser to find out. The API response already includes the parent key (\`Fields.Parent\`), it just wasn't being rendered. This adds a \`👪 <PARENT-KEY>\` entry to the header line, right after the issue key, but only when a parent exists so unparented issues (epics, top-level stories) keep the existing layout unchanged. Addresses ankitpokhrel#766.
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
1 participant
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.
When an issue has a parent, `jira issue view` currently gives no indication of it — you'd have to open the issue in the browser to find out. The API response already includes the parent key (`Fields.Parent`), it just wasn't being rendered.
This adds a `👪 ` entry to the header line, right after the issue key, but only when a parent exists so unparented issues (epics, top-level stories) keep the existing layout unchanged.
Addresses ankitpokhrel#766.