Wrike and GitHub Sync: Overview
Note
The Wrike and GitHub 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 GitHub sync is part of the Wrike Sync add-on. It enables automatic updates between Wrike tasks and GitHub issues. Select a GitHub repository that you'd like to sync with Wrike:
-
A new folder is created in Wrike (this folder is linked with the GitHub repository).
-
A task is created in Wrike for each issue in the GitHub repository.
-
For any task created in or added to the synced folder, a GitHub issue is created in the synced repository.
Once the sync is done, Wrike tasks are linked with corresponding GitHub 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.
Note
Only GitHub organization owners can connect to Unito. Members won't be able to connect. If your organization has enabled third-party application restrictions, you can follow this step-by-step guide for approving third-party apps in GitHub.
Tip
This page explains how the sync works and what you can do once the sync is in place. To learn more about setting up the sync, please see Wrike and GitHub Sync: Setup Guide.
-
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 GitHub data and build consolidated timelines, workload views, and dashboards that integrate Wrike and GitHub information.
After you set up a sync: If a change is made to a synced item in Wrike or GitHub, then the corresponding task or issue in the other tool is updated within five minutes.
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.
-
Adding comments: Comments are always synced, but the name of the person who made the comment is only synced if that person has an account in both tools.
-
Attachments: Attachments may also be synced. Unito supports binary copy attachments to and from GitHub Cloud or Server on a per-customer basis. To see all supported file types and get help with activation, please visit Unito’s Help Center page.
-
Managing assignees: Add, remove, or change assignees.
Note
Users can only be added as assignees in Wrike or GitHub 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 GitHub, then they won’t be assigned to the corresponding GitHub issue.
For more details on how fields are mapped between GitHub and Wrike, please refer to the section below.
There are two ways to create GitHub issues from Wrike:
-
Open the synced Wrike folder (the folder where GitHub issues are added) and create a task in that folder.
-
Open an existing task and tag it in the synced Wrike folder.
An issue (based on the task) is created in the synced GitHub repository within five minutes.
Currently, there are limitations when syncing Wrike subtasks with GitHub. Unito may help you with a workaround, you can contact them via their Help Center.
The following 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 |
GitHub |
|
Task title |
<-> |
Issue title |
|
Description |
<-> |
Issue description |
|
Status |
<-> |
State |
|
Comments |
<-> |
Comments |
|
Assignees |
<-> |
Assignees |
|
Due date |
<- |
Milestone due date |
|
Attachments |
-> |
Description footer |
|
Description footer |
<- |
Link to issue |
|
Description footer |
<- |
Milestone |
|
Description footer |
<- |
Author |
|
Custom field or description footer |
<- |
Issue type |
|
Description footer |
<- |
Labels |
|
Author |
-> |
Description footer |
|
Custom field |
-> |
Description footer |
|
Duration |
-> |
Description footer |
|
Importance |
-> |
Description footer |
|
Link to task |
-> |
Description footer |
-
Wrike task dependencies
-
Wrike time tracking
-
GitHub checklists
-
GitHub Projects
-
Mentions
Note
-
Unito doesn’t sync or modify code within pull requests. You can't create new pull requests from another tool, but you can keep them in sync with an equivalent work item.
-
You can sync open-source repositories. But assignees will only sync if their email address is present in Wrike.
-
Unito can't sync a repository if it was forked from another repository.
-
To learn more about it, please visit Unito’s help center.
If a field you'd like to sync isn't listed, please contact Unito. They may support it through a manual configuration.
Note
GitHub labels can't be mapped with all other fields. They will only work with similar fields, such as tags in Asana or labels in Trello. To learn more about it, please visit Unito’s help center.
Note
Ensure tasks are assigned to the correct people by mapping your GitHub and Wrike users together. Additionally, Unito requires workspace members to have certain read and write permissions in GitHub. To learn more about it, please visit Unito’s help center.