Repository navigation
Show the parent key in the issue view header - #1019
Open
ChrisJr404 wants to merge 1 commit into
Open
ChrisJr404 wants to merge 1 commit into
ChrisJr404 wants to merge 1 commit into
Conversation
When an issue has a parent, such as a sub-task or a story under an epic, show the parent's key in the view header next to a family marker. Issues without a parent render exactly as before. Closes 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.
This adds the parent's key to the header when you run
jira issue viewon an issue that has one, which covers the request in #766.At the moment there's no way to tell from the view screen whether a ticket is a sub-task or sits under an epic without opening it in the browser. When the issue has a parent I append its key to the first line of the header next to a 👪 marker, e.g.
… 🧵 0 linked 👪 EPIC-1. Issues without a parent render exactly as before, so existing output is unchanged.The GET
/issueendpoint already returns theparentfield and it's already on theIssuemodel (used elsewhere by clone/edit), so this just surfaces it in the view. Added a test ininternal/viewcovering both cases.make lintandmake testpass.