Start a fix from a Jira issue

Start it

From Jira: add the autofix label, or the label your project uses, to an issue in a switched-on project. You can add it when you create the issue or at any time later.

From the app: in the last Setup step, type the issue key and start the fix. Label2Prod adds the label for you and opens the fix in the app.

The issue should say what goes wrong and how to see it. For bugs, the bug report template covers everything Label2Prod needs, so it never has to ask.

What you see in Jira

Every update is a new comment. Label2Prod never edits an earlier one.

• Right away, a comment that it picked the issue up.
• If something is missing, its questions. Reply with a new comment and it picks the work up again, with the label still on. Editing the description does not restart it.
• When the change is proven, a comment with a link to the merge request, and the merge request linked on the issue.
• If it stops without a merge request, a comment saying why and what you can do next. That attempt does not count as one of your fixes.

Follow it in the app

Open Fixes to see every fix and its status. Each fix has a timeline of what happened, and what the attempt spent on your Anthropic key.

Stop a fix

Remove the label from the issue, or open the fix in the app and choose Stop this fix. Either works until the merge request exists. After that, close the merge request if you do not want it.

Give a hard issue more room

Add the autofix-deep label instead of autofix. The attempt can then use up to $30 on your Anthropic key instead of $12, and it still counts as one fix. When an attempt runs out of room, Label2Prod’s comment suggests this.

Try again

After a fix ends without a merge request, improve the issue, then remove the label and add it again.