Wrike + Jira Integration

Here’s an overview of Unito’s integration between Wrike and Jira, including use cases, mappable fields, and options for customization.

In this Article:

• A demo of Unito's Wrike Jira integration
• Which fields can Unito sync?
• What can't be synced?
• Customization options 
• Text formatting

Wrike and Jira, when used in combination, allow for seamless collaboration between business and technical teams. Here's how these two tools come together with Unito.

Watch Unito's Wrike Jira integration in action:

Which fields can be synced between Wrike and Jira?

Not seeing the fields you want? Contact us - we may already support them through a manual configuration.

What can't be synced between Wrike and Jira?

• Wrike task dependencies

• Wrike time tracking

• Jira links/dependencies

Customization options between Wrike and Jira

Here are all the available options for customization in Unito's Wrike + Jira integration:

• Filter synced work items: Unito will sync all items by default but you can customize your workflow by syncing just some of them. 
• Filter by Issue Type: Choose exactly which issue types sync from Jira.
• Include Subtasks: Enable seamless syncing of subtasks between Wrike and Jira.
• One-Way Syncing: Change flow direction to sync updates from Wrike to Jira, or from Jira to Wrike – your choice! 
• Map Users for Accuracy: Ensure tasks are assigned to the correct people by mapping your Jira and Wrike users together.
• Sync Closed Items: While Unito syncs open items automatically, you can also include closed items created before your workflow setup. 
• Add Jira Issue Number as Prefix: Easily reference Jira issues by automatically adding Jira issue numbers to task titles. 
• Choose Default Jira Issue Type: Control what issue type is used when new tasks originate in Wrike.

Text formatting between Wrike and Jira:

Unito translates rich text formatting between tools, keeping your task descriptions fully synced. However, there are some formatting options that are only partially translated from one platform to the other, while a few options are not supported entirely. Here is an explanation in greater details:

Formatting supported in both tools

The following is a list of the formatting options that are supported in both Wrike and Jira task descriptions. These options are preserved by Unito when syncing.

• Headings (levels 1 through 6)

• Bold

• Underline

• Italic

• Strikethrough

• Hyperlinks

• Unordered Lists

• Tables

Formatting partially supported

Some formatting in Wrike or Jira is only supported in part by Unito when syncing.

• Jira panels will be transformed into tables within Wrike.

• The table headers in Jira will be transformed into regular table cells in Wrike, but with bold formatting.

• Wrike’s checkboxes will appear on Jira but will not be clickable.

• Indented text in Wrike will be transformed into a bulleted list in Jira.

Markdown Preservation

The following Jira formatting is not supported in Wrike, but the flow will preserve the “markdown” when it shows up in Wrike.

• Colored text {color}
  Example:
   - In Jira : this is red text. I love it.
   - In Wrike: this is {color:#d04437}red text{color}. I love it

Other formatting markdowns preserved:

• superscript ^text^

• subscript ~text~

• preformatted text #

• paragraph quotes bq.

• block quotes {quote}

• emojis

• code {code}

• unformatted text {noformat}

• horizontal rulers

Formatting not supported

The formatting elements in this list will be lost when syncing. The original description will preserve its formatting of these elements as long as the description is not modified on the other side.

Wrike formats not supported in Jira:

• Text highlighting

Jira formats not supported in Wrike:

• NoneCustom Field or Description Footer