Label a Jira issue. Get a tested fix. No developer skills required.
Label2Prod does the engineering: it writes the fix and a test that proves it, then opens a GitLab merge request
that explains the change in plain words. You decide whether it ships.
Example: a Jira issue with the autofix label becomes a GitLab merge request, with a new test that
fails before the fix and passes after it.
Label addedProblem reproducedFix writtenTests passedMerge request opened
Projects / Shop / SHOP-812
Bug
Checkout: discount code is applied twice after the page is refreshed
Steps to reproduce
Add a €100.00 item to the cart
Apply SAVE10: the total is €90.00
Refresh the page: the total is €81.00
Activity
Label2Prod· just now
Picked this up. Reproducing the problem now.
Label2Prod· 14 min
Opened merge request !214. The new test fails before the fix and passes after it.
Labels
autofix
Component
shop-web
Priority
High
Reporter
QA team
acme / shop-web / !214
fix(SHOP-812): apply a discount code once per order
Openautofix/SHOP-812-1 → main
OverviewCommits 1Pipelines 1Changes 2
What was wrong
Refreshing the payment page sent the discount code a second time.
Verification
New test, before the fix Fails
New test, with the fix Passes
Full test suite 128 passed
✓ Pipeline passedApproveMerge
The difference
You don’t need to be a developer to deliver.
Most AI coding tools are built for developers: they live in a code editor or a terminal and expect you to read
code. Label2Prod starts where the problem is described, the Jira issue, and does the engineering for you.
Product owners turn small stories, tasks and bugs into changes ready to approve.
Founders keep shipping without waiting for engineering time.
Delivery and project managers follow every fix in Jira, with a complete record of what changed and why.
QA and support teams take the issue they filed all the way to a tested fix.
A person still approves every change. It just doesn’t have to be a developer: the merge request
says in plain words what was wrong, what changed and how it was proven.
GitHub Copilot for Jira works only with repositories on GitHub. Atlassian’s Jira coding agent, Rovo Dev, needs
Bitbucket Cloud or GitHub Cloud. GitLab Duo starts from GitLab issues, not Jira issues. Label2Prod is built for
the teams in between: issues in Jira Cloud, code in GitLab.
No. You need to know what is wrong, not how to fix it. Describe the issue in Jira and add the label; Label2Prod does the engineering and explains the result in plain words. Someone on your team with merge rights in GitLab approves the change, and the proof is there for them to see without reading code.
Do I need to install anything?
No. There is no IDE, no terminal and no copy of the code on your computer. You set Label2Prod up in your browser, and the work happens in Jira, in GitLab and in an isolated sandbox in your Anthropic account. Why that matters.
What does Label2Prod cost?
Nothing during early access, and no credit card. Fixes run on your own Anthropic API key, so Anthropic bills that usage to you directly. How early access works.
Which Jira issues can it work on?
Any issue type you turn on for a project. Bugs are on by default; tick Task or Story in settings to include them. The change must fit in one repository and be provable with a test.
Does it merge anything on its own?
No. Label2Prod pushes to its own branch, opens a merge request and stops there. A person on your team approves and merges it, under your own branch protection.
What if the issue leaves something out?
Label2Prod asks its questions in a comment on the issue. Reply with a new comment and it picks the work up again. For bugs, the bug report template covers what it needs.
Can I ask for changes to the merge request?
Yes. Comment @autofix followed by what to change, in plain words. Each request adds a new commit, as many times as you need in the first 24 hours after the merge request opens.
What about hard issues?
Use the autofix-deep label instead. The attempt can then use more of your Anthropic credit, and it still counts as one fix.
Where does my code go?
Each attempt runs in an isolated sandbox in your own Anthropic account, which is deleted when the attempt ends. Security details.
Start with your next Jira issue
Label2Prod is free for early-access teams, and you don’t need to be a developer. Connect Jira and GitLab, add the label, and approve the tested result.
Label2Prod · just now
Picked this up. Reproducing the problem now.