All articles

Wrike and Bitbucket Sync: Overview

Table 9. Available as a paid add-on


Overview

Note

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

The Wrike and Bitbucket sync is part of the Wrike Sync add-on. It enables automatic updates between Wrike tasks and Bitbucket. Once you select a Bitbucket repository that you'd like to sync with Wrike:

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

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

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

Note

The Wrike and Bitbucket two-way sync works with Bitbucket.com. Because of API limitations, we're unable to support on-premise installations of Bitbucket.

Once the sync is done, Wrike tasks become linked with corresponding Bitbucket issues, and when you update a linked task, the linked issue is automatically updated as well (and vice versa). Your teams can 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 Bitbucket 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 Bitbucket data and build consolidated timelines, workload views, and dashboards that integrate Wrike and Bitbucket 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 Bitbucket, then the corresponding task or issue in the other tool is updated within five minutes. The sync can be manually refreshed via the Syncs portal.

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 in Wrike or Bitbucket if they have a user license in that tool. For example, if a user is assigned to a synced Wrike task, but doesn’t have a user license in Bitbucket, then they won’t be assigned to the corresponding Bitbucket issue.

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

Create Bitbucket issues from Wrike

There are two ways to create Bitbucket issues from Wrike:

  1. Open the synced Wrike folder (the folder where Bitbucket 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) will be created in the synced Bitbucket repository within five minutes.

Subtasks and the Bitbucket integration

Default settings

Once a Bitbucket 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 Bitbucket, the issue remains an issue and isn't converted into a subtask.

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

Syncing subtasks

Bitbucket doesn’t have subtasks so you won't be able to sync them.

Mapped and unmapped fields

Mapped fields

The fields below 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

Bitbucket

Title

<->

Title

Description

<->

Description

Status

<->

Status

Comments

<->

Comments

File attachments

<->

File attachments

Assignees

<->

Assignees

Importance

<->

Priority

Custom field or description footer

<->

Issue type

Description footer

<-

Link to issue

Note

Syncing Bitbucket pull requests isn't currently supported by Unito's integration.

What can't be synced between Wrike and Bitbucket?

  • Wrike task dependencies

  • Wrike time tracking

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 in Wrike or Bitbucket if they have a user license in that tool. If a user has both a Wrike and Bitbucket account and uses the same email for both, they are automatically assigned to the synced item in the other tool when assigned in one.If a user has both a Wrike and Bitbucket account but uses different emails, you need to manually map their accounts.

Top