We use project boards in Asana. Multiple software teams use the same board. (Front-end team and back-end team)
It would be easier for our entire team and product owners to understand where we are in our workflow if Asana would allow us to link multiple Github Pull Requests to an Asana task. We may have changes to multiple repositories to solve a specific problem as written by a business user. Technically, if we need to resolve that problem in a front-end application and 6 micro-services and a host, we’re looking at at least 7 pull requests, as we are not in a mono-repo. While we could create a subtask for each and every area package where we change software, first that’s unnecessary overhead for engineers (as no one else is going to understand how to subtask technical concerns) and second, it is harder for business-level product owners to track how close we are to being finished with a task, across multiple development groups.
We have seen this integration work well in JIRA. We recently moved from JIRA to Asana, and this is quite an annoyance for our engineering teams. The impact is that subtasks have to be created for every package that an engineer touches. And it is noticeably more difficult for business users to glance at progress in a project board view w/out being able to see multiple PRs on a task.
The work we are considering having to do outside of Asana, is to build an asana action in each and every github repository that uses the Asana API to put a comment that a PR has been opened in the comments section (and closed if we desire to do that). However, that view will inevitably get cluttered with other conversations and requirement clarifications. We know this won’t sustain us very long at all.
Would you consider bringing Asana up-to-date with JIRA’s integration of this? They allow multiple PRs to be associated with a task.