Repository navigation
[Feature]: Reply to an existing comment thread with jira workitem comment create #28
Description
Problem or opportunity
twg jira workitem comment create can only add top-level comments to a work item. There is no way to post a comment as a reply inside an existing comment thread. When an agent answers a specific comment, the answer lands at the bottom of the issue and loses its link to the comment it responds to.
The other products already support this: twg bitbucket pull-requests comment create --reply-to <id> and twg confluence content comments reply --comment-id <id>. Jira is the odd one out.
Proposed outcome
Add a reply option to twg jira workitem comment create, for example --reply-to <commentId> (consistent with the Bitbucket command), so the new comment is created as a reply in that comment's thread. Comment IDs are already available from twg jira workitem comment query.
If Jira's API does not expose threaded replies, saying so in the command help would also help.
Area
CLI command behavior
Current workaround
Post a top-level comment that quotes or mentions the original comment's author. The thread structure is lost.
twg 1.3.5, macOS arm64
Activity
wallrj-cyberark commentedon Nov 6, 2026
This is still the case in twg 1.3.9 on Linux amd64. Jira does model threaded comments, so the gap appears to be only in twg:
JiraComment.threadParentId.comment createposts to REST v3/issue/{key}/commentwith a fixed body ofbody,propertiesandvisibility.--variables-jsononly passespropertiesthrough.Commentschema has no parent or thread field.So
--reply-toprobably needs the GraphQL mutation that the Jira UI uses for replies, or a REST field that is not documented yet.Until then, #35 adds a note to the twg-jira skill, so agents link the comment they are answering instead of looking for a reply option.