Note: I considered opening a discussion first but I have no prior experience with GitHub discussions and no judgment if it would be more appropriate or not. Happy to move it there if you prefer, let me know!
Is your feature request related to a problem? Please describe.
I use jira-cli heavily in my workflow, including in scripts and automation. A pattern I've run into a few times is maintaining a "living document" in a Jira comment — for example, an implementation plan that gets updated as work progresses. Since the only available comment operation is jira issue comment add, every update creates a new comment. After a few iterations I end up with a thread full of outdated snapshots, and the relevant one is buried at the bottom.
To work around it I had to fall back to the Jira REST API directly (curl -X PUT /rest/api/2/issue/{key}/comment/{id} and curl -X DELETE ...), which breaks the nice CLI-first workflow and requires wiring up auth separately.
Describe the solution you'd like
Two new subcommands under jira issue comment:
jira issue comment update <ISSUE-KEY> <COMMENT-ID> [--body "..."] [--template FILE] — edit an existing commentjira issue comment delete <ISSUE-KEY> <COMMENT-ID> — delete a comment
These would mirror the patterns already established by jira issue comment add (e.g. --template for multi-line bodies, --no-input for scripting).
Describe alternatives you've considered
- Direct REST API via curl — works but requires managing auth separately and loses the ergonomics of the CLI.
- Adding a new comment each time — creates comment noise; makes it hard to know which version is current.
Additional context
I'd genuinely be happy to contribute this if it sounds like something you'd welcome in the project. The comment add flow is already a good reference to follow. Just wanted to check first before investing time in a PR — no pressure at all if it's not in scope!
Is your feature request related to a problem? Please describe.
I use jira-cli heavily in my workflow, including in scripts and automation. A pattern I've run into a few times is maintaining a "living document" in a Jira comment — for example, an implementation plan that gets updated as work progresses. Since the only available comment operation is
jira issue comment add, every update creates a new comment. After a few iterations I end up with a thread full of outdated snapshots, and the relevant one is buried at the bottom.To work around it I had to fall back to the Jira REST API directly (
curl -X PUT /rest/api/2/issue/{key}/comment/{id}andcurl -X DELETE ...), which breaks the nice CLI-first workflow and requires wiring up auth separately.Describe the solution you'd like
Two new subcommands under
jira issue comment:jira issue comment update <ISSUE-KEY> <COMMENT-ID> [--body "..."] [--template FILE]— edit an existing commentjira issue comment delete <ISSUE-KEY> <COMMENT-ID>— delete a commentThese would mirror the patterns already established by
jira issue comment add(e.g.--templatefor multi-line bodies,--no-inputfor scripting).Describe alternatives you've considered
Additional context
I'd genuinely be happy to contribute this if it sounds like something you'd welcome in the project. The comment add flow is already a good reference to follow. Just wanted to check first before investing time in a PR — no pressure at all if it's not in scope!