Write-back
Linear, Jira and GitHub triggers can report back to the issue at three moments. In the trigger editor, Write back to the issue has one row per moment:
| Row | When | Stored as |
|---|---|---|
| Run starts | Right after the run is created | onStart |
| Succeeds | The run finished with status succeeded | onSuccess |
| Fails | The run finished failed or cancelled | onFailure |
Each row has a Post a status comment toggle and a Move to dropdown. New tracker triggers have comments on for all three rows and Don’t move selected. Schedule and webhook triggers don’t write back.
Comments
Section titled “Comments”The start comment is:
👋 Jimothy started run #42 (Feature: Plan → Build → Review → PR).The success/failure comment is a run summary:
✅ Jimothy run #42 succeeded (Feature: Plan → Build → Review → PR) in 18m 4s · $1.37Branch: jimothy/eng-123PR #57: https://github.com/acme/web-app/pull/57
✓ Plan✓ Implement✓ Run tests✓ Cross-model review✓ Human approval✓ Open pull request- The first line uses ✅ for success, ⏹️ for cancelled and ❌ for failed, and includes duration and cost when known.
Branch:appears if the run has a branch.- One line per link Jimothy found in step outputs: GitHub pull requests (
PR #57), GitLab merge requests (MR !12), Bitbucket pull requests, and*.vercel.apppreviews (Preview). - One line per step: ✓ succeeded, ✗ failed (with the first 200 characters of the error), – skipped, ⏹ cancelled.
On Jira Cloud the text is converted to Atlassian Document Format; on Linear and GitHub it’s posted as Markdown.
Transitions
Section titled “Transitions”Move to lists the stages your tracker actually has, loaded from the trigger’s account once you pick one:
| Platform | What the dropdown lists | What happens |
|---|---|---|
| Linear | The workflow states of the trigger’s team (or every team’s, if no team is set), in board order. | The issue moves to that state. |
| Jira | The statuses of the trigger’s Jira project, in workflow order. Without a project, every status on the site. | Jimothy applies the transition that leads to that status, if one is available from the issue’s current status. |
| GitHub | Under State: closed and open. Under Add label: the repository’s existing labels (create a label in GitHub first to use it). |
closed closes the issue, open reopens it, a label is added. |
- Don’t move leaves the issue where it is.
- A saved value the tracker no longer lists (a renamed status or deleted label) still shows, marked (not found), so saving the trigger doesn’t silently drop it. Pick a current one to fix it.
- If the stages can’t be loaded (for example the account lacks permission), the editor says Couldn’t load statuses with the error, and each row falls back to a text box. Values are matched case-insensitively: a Linear state name, a Jira transition or status name, or for GitHub
closed,openor a label name.
When a row has both, the comment is posted first, then the transition.
A typical setup
Section titled “A typical setup”| Row | Comment | Linear / Jira: Move to | GitHub: Move to |
|---|---|---|---|
| Run starts | on | In Progress |
jimothy:running |
| Succeeds | on | In Review |
jimothy:done |
| Fails | on | Todo (or Don’t move) |
jimothy:failed |
Pair the start transition with a trigger filter that excludes the target state, so the issue leaves the filter as soon as work starts.
When write-back fails
Section titled “When write-back fails”Write-back never affects the run itself. If a comment or transition fails, the error is recorded on the trigger (the Triggers page shows it in red and the Dashboard marks the trigger error) and sent as a Trigger errors notification:
Write-back to ENG-123 failed: Linear workflow state "In Reveiw" not foundWrite-back to WEB-45 failed: No Jira transition to "In Review" (available: In Progress, Done)Write-back to web-app#42 failed: HTTP 403 Forbidden from api.github.com: …Common causes:
- Stages that changed. A state or status renamed after the trigger was saved shows as (not found) in the editor. Linear needs an existing state name in that issue’s team.
- Jira workflow rules. Only transitions valid from the issue’s current status are available. A transition that works from To Do may not exist from In Progress. The error lists what was available.
- Read-only credentials. Comments and transitions need write access: Linear key with Write, Jira Add comments / Transition issues, GitHub Issues: Read and write.
- The account was removed or changed platform. Triggers need an account of the same platform.
The next successful poll clears the error.