Issue
Receive new issue-opened events from the selected GitLab project with Actions prefilled to open. Confidential-issue events, merge requests and later issue changes are outside this source selection.
Workflow template
Route newly opened GitLab issues into a Jira Cloud backlog. Copy the summary and project, issue number, author, creation time and source link while keeping descriptions, comments, attachments and code in GitLab.
How it works
Receive new issue-opened events from the selected GitLab project with Actions prefilled to open. Confidential-issue events, merge requests and later issue changes are outside this source selection.
Create a Jira Cloud issue with the original title as summary and a source metadata/link description. Select site, project and a standard issue type; no assignee, sprint or priority is mapped.
The result
Improve onboarding — Grüße aus Hamburg
GitLab project: example-studio/example-portal GitLab issue: #42 Opened by: alex-example Created: 2026-11-15T09:00:00Z Open original issue: https://gitlab.com/example-studio/example-portal/-/issues/42 Issue description, comments, attachments, and code stay in GitLab.
Illustrative source-sample summary and description. A real Jira key, status and priority depend on the selected project and are not claimed by this example.
Before activation
Connect GitLab, choose the project and keep Actions set to open. Confirm which non-confidential issue titles and metadata may be shared with the Jira audience.
Connect Jira with permission to create issues. Choose a standard issue type, not a subtask that also needs a parent; satisfy the destination project’s required fields.
Activate and wait for the source webhook to connect. Open a fictional issue in the selected project and compare its title, metadata and link in the new Jira issue.
The recipe creates one-way backlog items. Existing issues, confidential-issue events, merge requests, edits, reopenings and status changes are not synchronized. It does not keep Jira and GitLab statuses or comments aligned.
Project requirements still apply. Site, project and issue type start blank. The template sets no assignee, sprint or priority; Jira project defaults and required fields can affect creation. A subtask would additionally need a parent.
A link does not grant GitLab access. The Jira project audience sees the copied summary and metadata. Descriptions, attachments, comments and code stay in GitLab. Manual reruns or ambiguous failures can create duplicate Jira issues.
Use a standard issue type for the prepared recipe. A subtask also requires a parent, which is not mapped; the selected Jira project’s other required fields still apply.
No. This recipe handles newly opened ordinary issue events from the selected GitLab project. Confidential-issue events and merge requests are outside the source selection.
None are mapped by the template. The chosen project’s defaults and required-field rules apply. The summary uses the GitLab title, while the description contains metadata and the source link.
No. This is one-way issue creation for new open events. Existing items, edits, reopenings and status changes are not synchronized; rerunning an event can create another Jira issue.