Don't force KEY column in plain issue list output - #2
Merged
Conversation
IssueList.header() always prepended the KEY column when it was missing from --columns, even in --plain mode. KEY is only needed by the interactive TUI to drive view/move/copy actions, so plain output (which has no such actions) should respect the user-supplied column list as-is, including omitting KEY entirely.
rethab
added a commit
that referenced
this pull request
Aug 5, 2026
IssueList.header() in internal/view/issues.go always prepended the KEY column to the requested --columns list whenever it wasn't already present, with no exception for --plain mode. This meant \`jira issue list --plain --columns type\` (for example) would still print a KEY column the user never asked for. KEY is only needed by the interactive TUI to drive its view/move/copy actions. Plain output has no such interactive actions, so this change only forces KEY in when not in --plain mode, and respects the user-supplied --columns list as-is otherwise, including letting KEY be omitted entirely. Addresses ankitpokhrel#747.
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.
IssueList.header() in internal/view/issues.go always prepended the KEY column to the requested --columns list whenever it wasn't already present, with no exception for --plain mode. This meant `jira issue list --plain --columns type` (for example) would still print a KEY column the user never asked for.
KEY is only needed by the interactive TUI to drive its view/move/copy actions. Plain output has no such interactive actions, so this change only forces KEY in when not in --plain mode, and respects the user-supplied --columns list as-is otherwise, including letting KEY be omitted entirely.
Addresses ankitpokhrel#747.