Jira Cloud
Connects through Atlassian’s own consent screen. One organization can connect several Jira sites, and you choose which projects are switched on.
Jira Cloud + GitLab
From a Jira issue to a GitLab merge request
For teams that plan in Jira Cloud and ship from GitLab. Map your Jira projects to GitLab repositories once; after that, a label on an issue is all it takes. You don’t need to be a developer, and there is nothing to install.
- Jira Cloud
- GitLab.com or self-managed
- Any GitLab tier
- Nothing to install
Jira Cloud
You add the label
- Anyone who can edit the issue starts a fix
- Questions and updates arrive as new comments
- The merge request is linked on the issue
Label2Prod
It does the engineering
- Reproduces the problem with a new test
- Writes the fix in the right repository
- Checks it with your whole suite on a clean copy
GitLab
You approve and merge
- A branch named after the issue
- A merge request that explains the change
- Your pipeline runs as usual
Set up once
How the two connect
Three connections, made in your browser in about five minutes.
GitLab
Connects with a token for your group, with the Developer role and the api scope. Every project in the group and its subgroups becomes available.
The map
Says which repositories each Jira project uses. A project can use several repositories, and a repository can serve several projects.
In Jira
The whole story stays on the issue
Someone adds the autofix label. Label2Prod comments that it picked the issue up, and adds a new
comment each time it has something to say: a question when the issue leaves something out, the merge request
when the change is proven, or why it stopped and what you can do next. It never edits an earlier comment.
In GitLab
A merge request anyone can approve
- A branch named after the issue, such as
autofix/SHOP-812-1 - What was wrong, how it was reproduced and what changed, in plain words
- A new test that fails before the change and passes after it
- Your own pipeline, as on any merge request; the source branch is deleted when you merge
Revisions
Ask for changes in plain words
To change something, comment @autofix followed by the instruction. Label2Prod picks it up within a
couple of minutes and adds a new commit, checked the same way as the first. Ask as many times as you need in the
first 24 hours after the merge request opens. Label2Prod never merges; that stays with your team.
The alternatives
Why not the built-in options?
GitHub Copilot for Jira only works with repositories on GitHub, and Atlassian’s Jira coding agent (Rovo Dev) needs Bitbucket Cloud or GitHub Cloud. GitLab Duo works in GitLab, but its agents start from GitLab issues, so teams copy Jira issues across by hand.
| Product | Starts from a Jira issue | Opens GitLab merge requests |
|---|---|---|
| Label2Prod | Yes | Yes |
| GitHub Copilot for Jira | Yes | No |
| Rovo Dev | Yes | No |
| GitLab Duo | No | Yes |
Do I need the GitLab for Jira Cloud app?
No. Label2Prod connects to Jira and GitLab directly. If you already use the GitLab for Jira Cloud app, the merge request also appears in the issue’s development panel, because the Jira key is in the branch name and the title.
Does my GitLab pipeline run on the merge request?
Yes, like on any other merge request. If the pipeline fails on Label2Prod’s change, it makes one repair attempt on its own.
Can one Jira project use several repositories?
Yes. Label2Prod picks the repository the issue names, in its text or its Components, and asks on the issue when it cannot tell. Each fix is one merge request in one repository.
Who appears as the author?
In Jira, comments appear under the account that connected the site, so connect with a service account. In GitLab, branches and merge requests come from the account behind the token you connect.
Does it work with self-managed GitLab?
Yes. Enter your GitLab URL when you connect the group; the instance must be reachable from the internet over HTTPS.
Connect Jira and GitLab in about five minutes
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.
- Free during early access
- No credit card
- Nothing to install
Label2Prod · just now
Picked this up. Reproducing the problem now.