Unito’s new multiway sync engine has made it possible for you to connect 2 or 3 or 10 or 100 different projects together to build the perfect workflow of your dreams & reach productivity nirvana.
For the last two years, we’ve been enabling users to build syncs like this:
Connect App A to App B and you’re off to the races.
Now there’s more. We overhauled our Sync Engine you can now connect more than two apps together. You can build any kind of workflow you want! This unlocks a completely new functionality. Connect projects across apps (and within apps) throughout your entire organization. The potential for customization is limitless!
Mirror, split and merge workflows
You can construct any kind of workflow that you want with Unito. The fundamental building blocks of any workflow consist of 3 kinds of sync: a mirror, a split, and a merge. Each of these is further customizable by a filter.
The Power of Unito’s Sync Engine
When creating more complex syncs, it’s worth taking a moment to think about how Unito works. We’re a sync engine where you can build a set of rules we follow to connect tasks across projects. These rules make the sync engine reusable and extensible. Once you’ve set up your engine how you want it, cards will sync and de-sync based on the rules you’ve made.
A mirror is the basic Project A ↔ Project B sync. It’s generally between two different apps (like Trello and Asana, for example). But it can also be between two projects in the same app. Users who are using JIRA Cloud might want to sync a project with someone else’s JIRA On Premise instance. “Single app” mirrors are easier than onboarding and offboarding teams into one tool.
Splitting takes a big body of tasks and splits them up into many projects. You can split up a large backlog using labels (or folders if you’re syncing to Wrike). Trello, GitHub ad GitLab also support filtering by milestone. The other apps we connect support labels / folders, and some support other means of filtering. (Filtering by assignee and milestone are beta features and will roll out to other tools soon!)
Once you’ve decided how you want to split, you need to decide where you want to send the split tasks. It can be handy to draw this out by hand first. That way you know what kind of tasks you want to end up in what location and keep it in mind while you set up your sync. No matter how crazy the goals, sync creation still occurs between two endpoints at a time. If you’re splitting a backlog up into 5 working projects you’ll need to make 5 separate syncs.
Merging is easier. The opposite of splitting, it’s when you want to pull tasks from many projects (and apps) into one place. You can pull together the most important tasks from all your teams using filters. This is a quick live executive dashboard of the health of an existing project. Best of all, it works no matter what tools your team is using to manage their part of a project.
Or you can create a flat view of all the work in a project for a PM to keep tabs on the pulse of her team’s work.
Putting it together.
You can use our new sync features like tinkertoys to build any kind of workflow you like. We have an enterprise tech client demoing a 10,000 seat PM app instance. They give every single engineer their own project space. They Merge these projects into a departmental project. The Merge requires the engineer label a given task as “Important” enough to sync his boss’ board. Then the boss does the same with tasks to sync to her boss. And then that VP shares the merged tasks from that board all the way up to the CTO. When the CTO leaves a comment or asks a question on a task, the engineer responsible for it gets it in his or her tool. The response syncs all the way back up the chain to the CTO. How cool is that?
What use cases can you think of for project merge & split with Unito? We’d love to hear about it! 🙂