Regular Users on paid subscriptions can enable the Wrike and Bitbucket Two-Way Sync. This feature is currently available as a free trial, but in the future, it will be a paid add-on.
⏱ 4 min read
- Important Information
- Use Cases
- Ongoing Sync: Update Time and Synced Actions
- Create Bitbucket Issues from Wrike
- Subtasks and the Bitbucket Integration
- Mapped and Unmapped Fields
The Wrike and Bitbucket Two-Way Sync allows automatic updates between Wrike tasks and Bitbucket. Select a Bitbucket repository that you would like to sync with Wrike and
- 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.
Once the sync is in place, Wrike tasks become linked with corresponding Bitbucket 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.
✋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: Setup Guide.
- The Wrike and Bitbucket Two-Way sync works with Bitbucket.com.
- 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 first sync, a Wrike sync account is automatically created for you. The sync account 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. More details below.
- Project Management - Project and Product Managers can coordinate projects across both tools and keep an eye on how projects are progressing.
- 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 to build consolidated timelines, Workload Views, and Dashboards that combine both Wrike & Bitbucket information.
After you setup 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.
Make any of the below updates in one tool and the corresponding update automatically occurs in the other tool:
- Creating tasks or issues.
- Changing a task or issue’s status (including closing or completing the task or issue).
- Updating the title or description.
- Adding, removing, or changing assignees*.
- Attachments may also be synced depending on sync settings.
✋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 they don’t have a user license in Bitbucket, then they won’t be assigned to the corresponding Bitbucket issue.
More details on how fields are mapped between Bitbucket and Wrike can be found below.
There are two ways to create Bitbucket issues from Wrike
- Open the synced Wrike Folder (the Folder where Bitbucket issues are added) and create a task in that Folder.
- Open an existing task and tag the task in the synced Wrike Folder.
An issue (based on the task) is created in the synced Bitbucket repository within five minutes.
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 is not converted into a subtask.
- The Wrike subtask remains synced with the Bitbucket issue and the synced fields continue to automatically update.
Bitbucket doesn’t have subtasks so you will not be able to sync them.
The below fields are synced by default, please check Unito’s Help Center for more details on how to customize which fields are synced and how.
If a field you would like to sync is not listed please contact Unito, they may support it through a manual configuration.