All articles

Wrike and Bitbucket Sync: Setup Guide

Wrike and Bitbucket Sync is a part of the paid Project Syncs add-on. Admins on Business and higher plans can create the Wrike and Bitbucket two-way sync.

⏱ 4 min read

Overview

The Wrike and Bitbucket two-way sync allows automatic updates between Wrike tasks and Bitbucket issues. Select a Bitbucket repository that you’d like to sync with Wrike and:

  • Wrike creates a task for each issue in the Bitbucket repository.
  • For any task created in, or added to, the synced folder or project in Wrike, Wrike creates a Bitbucket issue in the synced repository.
  • When you update a linked task, the linked issue is automatically updated (and vice versa).

Please note: This page goes over how to sync tasks and issues between Wrike and Bitbucket. For details on what you can do once the sync is in place, please see Wrike and Bitbucket Two-Way Sync: Overview.

Important Information

  • 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.
  • To set up the sync with Wrike, it’s necessary to enable the Issue Tracker in the Bitbucket repository that is being synced. You can read more about enabling the Issue Tracker here.
  • The Wrike and Bitbucket two-way sync is powered by a partner: Unito.io. For even more information about how the two-way sync works, please check out Unito’s Help Center.
  • When you set up the integration, a Wrike Bot is automatically created for you. The bot doesn't take up a Wrike user seat. A sync account is not automatically set up in Bitbucket, and we strongly recommend creating one prior to setting up the first sync. You’ll find more details on how to do that below.

Set Up the Sync

Admins on Business and higher can enable the Wrike and Bitbucket two-way sync.

There are three steps to creating your first sync:

Step 1: Enable project syncs add-on in your Wrike account

Before setting up the two-way sync between Wrike and Bitbucket, you need to enable the Project Syncs Add-On in your Wrike account. You can find instructions on how to do that on the Project Syncs overview page.

Step 2: Create a Bitbucket test repository and sync account

Each sync setup begins with creating a folder or project in Wrike and a repository in Bitbucket that will be connected. To help you get a feel for how the sync works, create a test repository in Bitbucket and use it for your first sync.

Create a sync account in Bitbucket to better track when updates are made as a result of the sync. If you use a sync account and a user updates a task’s title in Wrike, then in Bitbucket you’ll see that the title of the synced issue was updated by the sync account. If you don’t use a sync account, then Bitbucket shows that a user (the user whose credentials you use to set up the sync) updated the issue.
To create a sync account, create a new Bitbucket user and name it “Wrike Bot.” Visit Unito’s Help Center to read more about what permissions the Wrike Bot account needs. Make sure you give the bot account access to the folder you want to sync.

Please note: You only need to create a sync account in Bitbucket. In Wrike, there’s a special bot called “Unito Bot for Two-Way Sync” that is automatically added to your Wrike account when you set up the integration.

Step 3: Sync setup between Wrike and Bitbucket

To create your first sync:

  1. Click your profile image in the upper-right corner of the Wrike account.
  2. Select “Apps and integrations.”
  3. Click the “Project syncs” tab in the left panel.
  4. (Optional) If there are multiple Wrike accounts associated with your email, select the relevant one.
  5. Click the “Add sync” button.
  6. You’ll see two cards on the screen for the two systems that you sync. The card on the right is reserved for Wrike by default.
  7. Click the “Add another tool” option on the left card.
  8. Select Bitbucket and you’ll be prompted to log in.
  9. Log in using the credentials of the bot account you created and authorize Unito.
  10. After connecting to your Bitbucket instance, you’ll be redirected to the sync.
  11. In the “Project” drop-down, select the existing Bitbucket repository you wish to sync or create a new one.
  12. After setting up the Bitbucket card, select a connector for Wrike on the right card:
    • The “Wrike via Unito Bot for Two-Way Sync” option is selected automatically. If you keep this option selected, Bitbucket will show that the bot has updated the issue. In this case, if you’re processing the first sync, you need to create a Wrike project or folder that will be integrated with Bitbucket. That project or folder will be available for selection in the future syncs.
    • If you choose “Wrike via Username” option, then the updates in Bitbucket will show that the user whose credentials you select to set up the sync updated the issue.
  13. After both cards are set up, scroll down to choose the preferred sync direction.
  14. Click “Next.” You’ll be directed to a page where you can configure filters.
  15. Leave the filters as is to sync all issues and tasks by default.
  16. Click “Next.”
  17. You’ll see the “Options” section. Here, you can disable Test Mode and Auto Sync and customize workflow and content.
  18. Click “Create sync” when all the preferred configurations are set up.

Your sync is created.

Please note: If you have a lot of existing tasks or issues, then it may take a few minutes for the first sync to be completed. Tasks and issues are added continuously until all of them are synced.

To sync additional Bitbucket repositories with Wrike, repeat the steps starting from Step 3 above.

Edit Existing Syncs

  1. Click your profile image in the workspace’s upper right-hand corner.
  2. Select “Apps and Integrations.”
  3. Select the “Bitbucket project Sync” card.
  4. Click the “Settings” button in the upper-right corner of the card.
  5. (Optional) If there are multiple Wrike accounts associated with your email, select the relevant one.
  6. Click the name of the sync to access its settings.

Now you can edit the sync.

0 comments

Article is closed for comments.

Top