Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

rtk jira: filtered output keeps trailing line padding — 30-39% of the result is spaces (v1.0.1)

Open Beginner friendly
  • Is something wrong?
#4,684 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@umi008 is already working on this.

Since Oct 21, 2026.

  • #4729 by @umi008 — open
  • #4736 by @ShryukGrandhi — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cli, rust
Domain
cli, devtools

Research direction

Start by reading the Jira filter added in #635 and trace the output path for jira issue view; the issue does not name a source file or test. Check how it handles line endings, trailing spaces, and blank lines, then verify the filtered output has close to 0% trailing padding while preserving the ticket content. The author is willing to send a PR, but is waiting for maintainer confirmation on the approach.

Written by the indexing model from the issue text.

Description

area:cli bug good first issue priority:low

Summary

The jira filter added in #635 (shipped v0.49.0) strips blank lines and separators, but leaves every line space-padded to the box width that jira-cli drew. On a terminal that wraps anyway, that padding is pure token cost: it is 30–39% of the filtered output.

Verified on v1.0.1 (homebrew, macOS arm64).

Measurement

Two real tickets, jira issue view <KEY> --plain through rtk:

Ticket rtk output of which trailing padding lines
A (29 lines) 3,321 chars 1,324 (39%) 29
B (43 lines) 4,878 chars 1,485 (30%) 43

Per-line, the first three lines of a filtered view:

1: len=111 trailing_spaces=22
2: len=118 trailing_spaces=23
3: len=114 trailing_spaces=30

Repro

rtk jira issue view <ANY-KEY> --plain | python3 -c "
import sys
t = sys.stdin.read()
pad = sum(len(l) - len(l.rstrip()) for l in t.split(chr(10)))
print(f'{len(t)} chars, {pad} trailing padding ({100*pad//len(t)}%)')
"

Expected: close to 0% padding. Actual: 30–39%.

Why it is worth a one-liner

rstrip() per line before joining. No behaviour change — the padding carries no information, the box borders are already stripped by the existing filter, and nothing downstream can depend on column alignment once the separators are gone. It is the single largest remaining cost in the jira filter's output, and it compounds on every issue view and issue list an agent makes.

A related, smaller one: runs of consecutive blank lines survive in some views; collapsing them to one is the same pass.

Note on #524

#524 was closed as completed on the strength of #635, which is fair — output is filtered now. This is not a regression of that, just the next layer down.

Happy to send a PR if a maintainer confirms the approach (plain rstrip on each line in the jira filter's output path) is what you'd want.

Dominant language
Rust
Stars
85k
Forks
5.4k
Avg merge
5d 23h
Merged PRs (30d)
60

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rtk-ai/rtk

All issues in rtk-ai/rtk

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.