What this article covers:

  • The value of an integration tool like Unito
  • How to use Unito to foster collaboration across Asana and GitHub
  • Recommended Unito settings

The value of an integration tool like Unito

More often than not, projects teams are assembled with cross-functional members who collaborate closely on a daily basis. For example, a project workflow may call for new features implemented by developers to be reviewed and accepted by the quality assurance or business members. However, putting different teams in the same room doesn’t mean they’ll collaborate efficiently. This can lead to a frequent topic for heated debate: which project management tool should we use?

It’s practically impossible to pick a tool that suits everyone’s taste, or more importantly, a tool designed for everyone’s specialized role.

A common scenario is for the business and creative members to choose Asana, while the tech team never want to leave their Github repositories. This guide will show you how to best use Unito to let cross-functional teams collaborate on projects directly from their tool of choice, whether it’s Asana or Github.

How to use Unito to foster collaboration across Asana and GitHub

1) Synchronize your existing Github repositories into Asana

If you don’t have a repository in Github yet, create one first. Then create a Sync in Unito.

Once the sync is created, you will have a new project in Asana with all the issues and tasks. The name of this new project will be "[github organization name]/[repository name]". Feel free to rename the project (but not the Github repo, it would break the sync!) and move it wherever you want in your Asana structure; it will stay in sync.

2) Pick the best settings for your teams to collaborate efficiently

Every team has its workflow and Unito offers a bunch of settings to make sure that your teams can work together efficiently.

Map your users

The most important one is mapping your assignees between Asana and Github to make sure everything assigned to someone in one tool gets assigned to the same person in the other tool!

Choose what to sync

You need to decide if you want every task or issue to be automatically synced, or if you want to filter certain types depending on their tag/label or type.
Think about it before enabling your sync because the filter will only be effective for the tasks synced after the filter creation.

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 outside the project. This makes personal planning that much easier.

Warning
Creating the sync with your personal connector can create some messiness between your team members, as every action in any of the tools will be synced according to your settings.

We strongly recommend creating a bot user and use it to sync your Github repos and Asana projects.

4) Get to work

Work out of your todo list, in your tool of choice, and get things done!

Now, any time you update a synced task or issue, the change will convert to the corresponding task or issue in the other tool. This includes comments, changing the state or assigning 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 during another status meeting.

Recommended Unito settings

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

  • Map your Asana and Github users, and have your tasks show up in your personal to-do list.
  • Enable attachment sync, and share specs, designs and screenshots with your team.
  • Prefix tasks with the Github issue number so everyone in Asana knows what comes from Github and can quickly find it there. Enable in Settings / Asana / Prefix task title with issue number.

What's next?

Learn how to sync multiple Asana projects.
Learn how to integrate Asana with Trello.
Not a Unito user? Try Unito for two weeks free!
Already a user? Sign in here!

Did this answer your question?