Jira smart commits not working (no transition/comment) in CI

Smart commits are processed by the Git integration (GitHub for Jira), not by CI. They fire only when the repo is connected to Jira and the commit message uses the exact ISSUE-123 #comment, #time, or #transition syntax.

What this error means

Commits reference an issue but no comment, worklog, or transition appears in Jira. The commit shows in the issue development panel or not at all.

git commit -m "ABC-123 #comment fixed the null check #time 30m #close"
# expected: comment + 30m logged + issue transitioned; actual: nothing happens in Jira

Common causes

The repository is not connected to Jira

Smart commits require the GitHub for Jira integration linking the repo to the site. Without it, Jira never sees the commits.

The commit message syntax is off

The issue key must be uppercase and followed by #command. A transition name must match a valid workflow transition, or the command is ignored.

How to fix it

Connect the repo and use exact syntax

1. Install and connect the GitHub for Jira app so commits reach the site.
2. Enable smart commits for the account performing the commits.
3. Write ABC-123 #comment ..., #time 2h, or #transition-name exactly.

git commit -m "ABC-123 #comment deploy fix #time 45m #resolve"

Match the transition command to the workflow

The word after # for a transition must resolve to a real workflow transition name for the issue current status, or it is silently skipped.

How to prevent it

• Keep the GitHub for Jira connection healthy for smart commits.
• Enforce uppercase issue keys and correct #command syntax in commits.
• Use explicit REST transitions in CI when you need guaranteed behavior.

Related guides