Wrike and JIRA Sync: Overview
Wrike and Jira Sync is a part of the paid Project Syncs add-on. Admins on Business and higher plans can create the Wrike and Jira two-way sync.
⏱ 4.5 min read
- Important Information
- Use Cases
- Ongoing Sync: Update Time and Synced Actions
- Create JIRA Issues from Wrike
- Subtasks and the JIRA Integration
- Mapped and Unmapped Fields
The Wrike/JIRA sync allows 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).
Please note: This page goes over how the sync works once it's in place, for details on how to set up the sync, check out our: Wrike and JIRA Two-Way Sync: Setup Guide.
- Tasks must remain in the synced Wrike folder in order to remain synced to a corresponding JIRA issue. A task can be tagged in additional folders, but if it is removed from the synced folder, then it stops being synced with JIRA.
- Individual team members only need a Wrike or JIRA license for the sync to work. They do not need licenses in both tools. For example, if someone updates a task in Wrike, the JIRA issue is automatically updated even though the user does not have a JIRA license.
- The Wrike and JIRA Two-Way Sync is powered by a partner: Unito.io. For even more information about how the Wrike and JIRA Two-Way Sync works, please check out Unito’s Help Center.
- 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 JIRA data and to build consolidated timelines, workload views, and dashboards that combine both Wrike & 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 below updates in one tool and the corresponding update automatically occurs in the other tool:
- Creating tasks, issues or epics.
- Changing a task or issue's status (including closing or completing the task or issue).
- Updating the title or description.
- Updating due dates or duration fields.
- 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).
- Adding, removing, or changing assignees.*
- Attachments and epics may also be synced depending on your sync settings.
*Please 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 they don’t have a user license in JIRA, then the corresponding JIRA issue will be unassigned.
More details on how fields are mapped between JIRA and Wrike can be found 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 the task 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 that 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 setup. Read more about how to change the default settings.
Automatically Mapped Fields
Unito uses the below fields to create Wrike tasks from JIRA issues or epics and vice versa.
|Due Date||Due Date|
*For more details, please visit the text formatting post on Unito’s site.
**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, then the corresponding field in the other tool automatically updates as well. When the original estimate is updated, then JIRA automatically recalculates the remaining estimate.
***Please note: 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 they use the same email with both tools, then when they are assigned to something in one tool, they are automatically assigned to the synced item in the other tool. If a user has both a Wrike and JIRA account, but they use different emails with each tool, then you need to manually map their accounts. Note that users with the same emails will be automatically mapped between Wrike and Jira if the users existed in both Wrike and Jira before the sync was created. After Wrike and Jira are synced, it will be necessary to add user mapping for all the new users manually. It's also possible to re-create a sync with the same settings to map all users with matching emails automatically.
Manually Mapped Fields
In addition to the fields above you can manually map:
- Custom Workflows in JIRA to Custom Workflows in Wrike.
- Priority in JIRA to Importance in Wrike.
- Custom Fields
Check out Unito's help center for more information about manually mapping fields.
All fields not mentioned above (including "issue type", "Resolution") are currently not synced.