All articles

Wrike and GitLab Sync: Overview

Table 7. Available as a paid add-on


Overview

Note

The Wrike and GitLab two-way sync is powered by our partner: Unito.io. For more information on how the sync works, please visit Unito’s Help Center.

The Wrike and GitLab sync is part of the Wrike Sync add-on, allowing automatic updates between Wrike tasks and GitLab. Select a GitLab repository that you would like to sync with Wrike and

  • A new folder is created in Wrike (this folder is linked with the GitLab repository).

  • A task is created in Wrike for each issue in the GitLab repository.

  • For any task created in or added to the synced folder, a GitLab issue is created in the synced repository.

Once the sync is in place, Wrike tasks become linked with corresponding GitLab issues and when you update a linked task, then the linked issue is automatically updated as well (and vice-versa). Your teams are able to collaborate effectively while remaining in the tool that they’re most familiar with.

Tip

This page explains how the sync works and what you can do after it's in place. To learn more about setting up the sync, please see Wrike and GitLab Sync: Setup Guide.

Use cases

  • Project Management: Project and product managers can coordinate projects across both tools and monitor project progress.

  • Team collaboration: Non-technical employees and developers can easily track project progress, answer questions, and share information.

  • Reporting and timelines: Use Wrike to report on GitLab data and to build consolidated timelines, workload views, and dashboards that integrate both Wrike & GitLab information.

Ongoing sync: Update time and synced actions

Update time

After you set up a sync: If a change is made to a synced item in Wrike or GitLab, then the corresponding task or issue in the other tool is updated within five minutes.

Synced actions

Make any of the following updates in one tool, and the corresponding update automatically occurs in the other tool:

  • Creating tasks, issues, or epics: New items created in one tool are mirrored in the other.

  • Changing status: Update a task or issue's status, including closing or completing it.

  • Updating titles or descriptions: Changes to these fields are synced across both tools.

  • Attachments: These may also be synced depending on your sync settings.

  • Managing assignees: Add, remove, or change assignees.

Note

Users can only be added as assignees if the GitLab account is a Maintainer or Owner in the GitLab project to configure webhooks.

For more details on how fields are mapped between GitLab and Wrike, please refer to the section below.

Create GitLab issues from Wrike

There are two ways to create GitLab issues from Wrike:

  1. Open the synced Wrike folder (the folder where GitLab issues are added) and create a task in that folder.

  2. Open an existing task and tag it in the synced Wrike folder.

An issue based on the task is created in the synced GitLab repository within five minutes.

Subtasks and the GitLab integration

Default settings

Once a GitLab issue is added to Wrike as a task, then you can convert the Wrike task into a subtask. Convert the synced task into a subtask of another synced task or add it as a subtask in a related, but non-synced, project. In either case, when you convert a synced task into a subtask:

  • Only the Wrike organizational structure is affected. In GitLab, the issue remains an issue and is not converted into a subtask.

  • The Wrike subtask remains synced with the GitLab issue and the synced fields continue to automatically update.

Syncing subtasks

GitLab doesn’t have subtasks so you will not be able to sync them.

Mapped and unmapped fields

Mapped fields

The below fields are synced by default, either one way or both ways. Please check Unito’s Help Center for more details.

<-> Synced both ways

-> / <- Synced one way

Wrike

Sync

GitLab

Title

<->

Title

Description

<->

Description

Comments

<->

Comments

Description footer

<-

Link to task

Attachments

->

Description footer

Due date

<->

Due date

Status

<->

Status

Description footer

<-

Author

Description footer

<-

Labels

Description footer

<-

Issue number

Description footer

<-

Milestone

Duration

->

Description footer

Importance

->

Description footer

Link to task

->

Description footer

Start date

->

Description footer

Custom field

->

Description footer

Custom field

<->

Weight

What can't be synced between Wrike and GitLab?

  • Wrike task dependencies

  • Wrike time tracking

  • GitLab merge requests

  • GitLab Priority

  • Mentions

Unmapped fields

If a field you'd like to sync isn't listed, please contact Unito. They may support it through a manual configuration.

Note

Users can only be added as assignees if the GitLab account is a Maintainer or Owner in the GitLab project to configure webhooks and needs to push or read/write access..

Top