Repository navigation
Fix Jira issue key column width being hardcoded - #2178
Merged
FelicianoTech merged 1 commit intoSep 29, 2026
Merged
Conversation
getLongestColumnLengths() assigned len("WTF-XXX") to longestKeyLength
instead of the issue key's actual length, with the correct value left
in place as a trailing comment:
longestKeyLength = len("WTF-XXX") // issueKeyLength
The row format pads the key to longestKeyLength+1, so the column was
always 8 wide. Any key longer than that overflows its field and shifts
every subsequent column left by the overflow, so projects whose keys
differ in length render ragged:
Bug GRID-11658 Ready [Triggered] critical celery task...
Task PROD-1901 In Progress necessary datamodel changes
Using the real key length restores the intended alignment:
Bug GRID-11658 Ready [Triggered] critical celery task...
Task PROD-1901 In Progress necessary datamodel changes
Issue keys have no equivalent of MaxIssueTypeLength/MaxStatusNameLength
clamping them, which is why this only affects the key column.
Adds tests covering the longest-key case, the equal-length case, and the
existing clamping of the type and status columns.
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.
Purpose
getLongestColumnLengths()inmodules/jira/widget.goassignslen("WTF-XXX")to
longestKeyLengthrather than the issue key's actual length. 7 characters is not enough for many Jira tickets.example of the bug:

Change this line to expand longestKeyLength to the maximum in the issue list, not a max of 7 characters
Add unit tests