jira-workitem-comment

Jira Workitem Comment

Add comments to Jira tickets using the acli CLI with support for both simple text and rich Atlassian Document Format (ADF).

Prerequisites

• acli must be installed and authenticated (acli jira auth)

Implementation

Step 1: Verify ACLi Setup

Before proceeding, verify that acli is installed and authenticated by invoking the acli-setup-check skill:

/acli-setup-check

If the setup check fails, stop execution and guide the user to fix the issue.

Step 2: Determine Ticket Key and Comment Content

1. Ticket Key:

   • If provided by user, use it
   • Otherwise, search conversation history for ticket references matching the pattern [A-Z]+-\d+
   • If not found, ask: "Which ticket should I comment on?"

2. Comment Content:

   • If the user provides comment text, use it
   • If the user wants to document a conversation or finding, infer the content from context
   • If unclear, ask: "What would you like to say in the comment?"

3. Comment Type:

   • Simple text: Default for straightforward comments
   • Rich format: Use when comment includes code blocks, lists, or structured content

Step 3a: Add Simple Text Comment (Default)

For plain text comments, write the comment text to a temporary file and use acli to create the comment:

# Validate ticket key format (PROJECT-NUMBER)
TICKET_KEY="<ticket-key-from-step-2>"
if [[ ! "$TICKET_KEY" =~ ^[A-Z]+-[0-9]+$ ]]; then
  echo "Error: Invalid ticket key format. Expected PROJECT-NUMBER (e.g., AIPCC-1234)"
  exit 1
fi

# Write comment to temp file (uses system temp directory)
TMPFILE=$(mktemp -t acli-comment-XXXX.txt)
cat > "$TMPFILE" << 'EOF'
<comment text goes here>
EOF

# Create the comment with validated ticket key
acli jira workitem comment create --key "$TICKET_KEY" --body-file "$TMPFILE"

# Clean up
rm -f "$TMPFILE"

Step 3b: Add Rich ADF Comment (For Formatted Content)

For comments that need rich formatting (code blocks, lists, mentions, links), construct an ADF JSON structure.