What this article covers:
- The benefits of triaging development requests through a project management tool
- How to build a development triage project in Asana
- Recommended Unito settings
The benefits of triaging development requests through a project management tool
IT and dev teams are bombarded by requests via email, chat, meetings, and cubicle drive-bys. Someone has to capture, sort, remove duplicates, and re-file these requests into the team’s issue tracking tool, which is GitHub more often than not.
If this overhead wasn’t enough, add the fact the requester doesn’t have (or want) access to the tracking tool for updates.
This guide will show you how to best use Unito to channel all requests made from Asana directly in GitHub, while keeping communications open between the Asana request and the resulting GitHub issue.
How to build a development triage project in Asana
1) Synchronize your GitHub repository into Asana
Since Unito performs two-way syncing, this rule will prevent any existing GitHub issue from becoming a new Asana task, while letting new Asana task requests become GitHub issues.
We recommend you type in a dummy GitHub label called "Asana-request" in the filtering field.
Once you SAVE & SYNC, Unito will create a new project in Asana for each of your GitHub repos. Any new tasks added to these projects will become a GitHub issue.
2) Submit new requests
Let your colleagues in Asana know of new request project(s), and submit-at-will!
Each new request will take the form of an Asana task, which Unito will synchronize into a GitHub issue. From that point on, any change made to the task or issue will be synchronized. The dev team can push the issue through their standard internal process directly from GitHub. This means Asana users can track, comment and get answers to the request without ever leaving Asana!
Recommended Unito settings
Try out these settings to get the most out of your workflow:
- Learn how rules work and what they can bring to your workflow.
- Make sure to sync file attachments so users can share screenshots or more
- Make sure to map tags and labels to have the same workflow on both sides