Wrike and Jira Sync: Overview
Note
The Wrike and Jira 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 Jira sync is part of the Wrike Sync add-on, allowing for automatic updates between Wrike tasks and Jira issues. Once a sync is in place:
-
Wrike creates a task for each issue or epic in the Jira project.
-
For any task created in or added to the synced folder, a Jira issue is created in the synced project.
-
When you update a linked task, then the linked issue is automatically updated (and vice versa).
Note
To set up the Wrike and Jira sync, ensure you have administrator access to your Jira instance to connect your Jira account to Unito. Once the account is connected, you only need project-level admin permissions to create a flow. For more information on connecting Jira and Unito, please see the relevant article in the Unito Help Center.
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 Jira 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 Jira data and to build consolidated timelines, workload views, and dashboards that integrate both Wrike and Jira information.
After you set up a sync: If a change is made to a synced item in Wrike or Jira, then the corresponding task or issue/epic 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.
-
Updating titles or descriptions: Changes to these fields are synced across both tools.
-
Updating due dates or duration fields: Adjustments to timelines are reflected in both tools.
-
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 and epics: 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 Jira 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 Jira, then the corresponding Jira issue will be unassigned.
For more details on how fields are mapped between Jira and Wrike, please refer to the section below.
There are two ways to create Jira issues from Wrike
-
Open the synced Wrike folder (the folder where Jira 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 Jira project. The time the sync takes depends on the Unito subscription you have. Users who set up the integration within Wrike have the “Free with Wrike” plan by default, which takes up to 5 minutes to sync the data. You can read more about the rest of the subscriptions here.
By default, Jira subtasks are not imported into Wrike. However, once a Jira 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 Jira, the issue remains an issue and is not converted into a subtask.
-
The Wrike subtask remains synced with the Jira issue, and the synced fields continue to automatically update.
You can change the default settings so that subtasks are imported and automatically synced between Wrike and Jira from the moment the sync is set up. Read more about how to change the default settings.
Unito uses the below fields to create Wrike tasks from Jira issues or epics and vice versa. They are either synced one way or both ways. Please check Unito’s Help Center for more details.
<-> Synced both ways
-> / <- Synced one way
|
Wrike |
Sync |
Jira |
|---|---|---|
|
Task title |
<-> |
Issue title |
|
Task description |
<-> |
Issue description |
|
Status |
<-> |
Status |
|
Comments |
<-> |
Comments |
|
Assignees** |
<-> |
Assignees |
|
Due date |
<-> |
Due date |
|
Duration* |
<-> |
Original estimated duration |
|
Importance |
<-> |
Priority |
|
Custom field or description footer |
<-> |
Sprint (name, start/end dates) NoteUnito can only sync Jira sprints that meet the following three requirements:
|
|
Attachments |
-> |
Description footer |
|
Description footer |
<- |
Attachments |
|
Description footer |
<- |
Link to issue |
|
Description footer |
<- |
Components |
|
Custom field or description footer |
<- |
Epic name and link |
|
Custom field or description footer |
<-> |
Issue type |
|
Description footer |
<- |
Labels |
|
Description footer |
<- |
Reporter |
|
Custom field or description footer |
<- |
Time tracking (time spent) |
|
Author |
-> |
Description footer |
|
Custom field |
-> |
Description footer |
|
Link to task |
-> |
Description footer |
|
Custom field |
<-> |
Custom fields |
-
Wrike task dependencies
-
Wrike time tracking
-
Jira links/dependencies
If a field you'd like to sync isn't listed, please contact Unito. They may support it through a manual configuration.
Note
*During the first sync, the original estimate (from Jira) is mapped to the Duration field in Wrike. If the Duration or original estimate fields are updated, the corresponding field in the other tool automatically updates as well. When the original estimate is updated, then Jira automatically recalculates the remaining estimate.
**Users can only be added as assignees in Wrike or Jira if they have a user license in that tool. If a user has both a Wrike and Jira 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 Jira account but uses different emails, you need to manually map their accounts. Note that users with the same emails will be automatically mapped between Wrike and Jira if they existed in both Wrike and Jira before the sync was created. After Wrike and Jira are synced, it will be necessary to manually add user mapping for all the new users. It's also possible to re-create a sync with the same settings to automatically map all users with matching emails.