Use Case: Business and Development Teams Collaboration in Wrike

Enhance cross-departmental teamwork by keeping business teams in Wrike and developers in Jira, all while maintaining a seamless flow of information.

What this article covers:

• The value of a work automation platform

• How to use Unito to foster collaboration across Wrike and Jira

• Recommended Unito settings

The value of a 2-way integration platform

Putting different teams in the same room doesn’t mean they’ll collaborate efficiently. It’s practically impossible to pick one that suits everyone’s taste, or more importantly, a tool designed for everyone’s specialized role. 

One possible scenario is for the business and creative teams to choose a popular project management tool such as Wrike, Asana, or monday.com, while IT management, software, or development teams stay in their preferred ServiceNow, Jira or GitHub interface.

Unito is designed to resolve this type of issue and enable cross-functional teams to collaborate on projects directly from their tool of choice. With a simple two-way flow, you can avoid purchasing multiple seats or having someone switch back and forth between work apps to keep teams updated.

All it takes is a simple 4-step process

1. Align Workflows: Create compatible workflows in your tools, in this case we'll use the example of Wrike and Jira. Similar status names (e.g., "In Progress", "Review") are ideal, but not strictly necessary.
2. Connect your tools to Unito: Create a Unito flow. Map your workflows and users to ensure tasks and assignees sync accurately.
3. Plan and Assign Tasks: Distribute work within your chosen tool. Unito ensures assignees are mirrored across platforms.
4. Work and Update: Team members work within their preferred tool. Comments, status changes, and reassignments sync in real-time between Wrike and Jira.

Expanded Use Case: Foster collaboration between Wrike and Jira with Unito

1) Create a custom workflow in Wrike

Since you’ll be collaborating closely on tasks and issues, possibly handing them off back and forth between the tools, it’s important that the workflows in both tools are compatible. Both Wrike and Jira support custom workflows; you should design them to have similar phases. It doesn’t mean they need to be exactly the same. However, a single state in one tool could break down into multiple more granular states in the other.

Compatible Wrike and Jira workflows

2) Sync an existing Jira project with Wrike

If you don’t have a project in Jira yet, create one first. Then create a Wrike Jira flow in Unito and make sure to customize it to filter by status you designed and associate your Wrike and Jira users.

Once the flow is created, you will have a new folder in Wrike with all the open issues as tasks. Feel free to move that project within the Wrike folder structure.

3) Assign each other tasks

Plan your project and dispatch the tasks. Assignees will sync between tools, so everything assigned to you will show up in your personal to-do list, side-by-side with any other task you may have, making personal planning that much easier.

4) Get to work

Work out of the to-do list; in your tool of choice, and get things done!

Now, any time you update a synced task or issue, the change will propagate to the corresponding task or issue in the other tool. This includes comments, changing the state or reassigning someone else. You can instantly see the progress of your team and project without ever leaving your tool of choice, and without bugging someone over chat, email or another status meeting.

Unito Best Practices

Try out these settings to get the most out of your syncs:

• • Workflow Mapping: Ensure smooth syncing by carefully aligning Wrike and Jira workflow statuses.
  • User Mapping: Match Wrike and Jira users for accurate task assignment across tools.
  • Attachment Syncing: Share documents and visuals effortlessly between teams.
  • Issue Prefixing: Enable the "Prefix task title with issue number" setting in Unito for quick Jira issue referencing in Wrike.