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.
11 Likes
Hi @Aaron_Cope, welcome to the Asana Community Forum 
Thanks for taking the time to provide this feedback!
While it’s not possible to link Asana to multiple requests at this time, hopefully it’s something our Product team can implement in the future.
I’ll keep you posted and let you know if we have any updates 
It was great for big companies with many teams which work on one product!
We would really love this!
We often have matching Github PRs for our back-end and front-end repos that both need to be complete before the Asana task can be considered ready.
We also moved from Jira and this was a basic feature that I would have expected Asana to have.
4 Likes
@Rebecca_McGrath have you heard back from your product team? This is a common use case in our company, more often than not you’ll have multiple pull requests for a single task
1 Like
I wholeheartedly second this. It’s really very, very common in our workflow to break down tasks into tiny PRs, so not being able to attach multiple PRs to a single task is a huge handicap.
2 Likes
Any updates on this? It’s a must-have feature.
5 Likes
For those above, my team creates subtasks for each PR, that way we can have multiple attached to the overall ticket.
Hello Asana Team, Any Updates on this Request, 2.5 years have passed and My Projects in Asana are also willing for this multilinking, also the autolinking like you do on JIRA with the task-no.## on the comment or on the branch will be awesome for it to autodetect it and autoadd is to the task
Just found this thread and was surprised that there hasn’t been any movement on this yet. We are considering to switch to something else that offers this functionality.
Is there any update on this?!
@Rebecca_McGrath I also think it’s a must have, any updates on a feature?
@Hendrik_Prinsloo , @Matt_Fisher5 , @Vladimir_Turov , welcome all to the forum .
Asana doesn’t make theor roadmap public, but if there is any movement on this feature request, it will get posted here.
In the mean time you could sync between Asana and Github using the native integration or a 3rd party integration like perhaps zapier.com or zzbots.com
Alternatively, you could get a developer to create an app for you that would use APIs.
@Matt_Fisher5 @Vladimir_Turov
Hey all,
I just learned today that my company spent 60+ hours building this integration between Asana and Github that syncs everything between the two systems because, as you all know, it’s a must-have feature.
I came looking for other people who might have this same issue. I had a feeling I’d find you!
When we plan a new feature, we build it out in Asana and assign a developer. They’ll open a branch in Github and open a pull request and link it to the Asana task. From there everything is fully synced, so when the code is submitted to review it is automatically moved to the review column in Asana and it automatically creates PR subtasks that are assigned to the correct people, which it gets from Github. As things get moved or closed out in Asana or Github, the other system automatically syncs. This includes all comments posted in either Asana or Github. When the code is ultimately merged into the main branch in Github, the Asana task is closed and mark complete.
I’m not a developer myself (I’m in marketing and do all my work in Asana) and despite assigning dev tasks to my team on occasion, I genuinely did not even know this sync existed at my company because the process is so seamless. I get notified in Asana when features are released and my dependent tasks are unblocked. I’ve never even opened Github before.
I confirmed with my founder that this is something we could package up and sell to other companies who need it, with some custom work to ensure alignment for other comanies’ specific use cases.
If you want to chat with my team about this, we’d be happy to help. Feel free to reach out to Amanda.Crooks@nsquared.io.
@Hendrik_Prinsloo @Cristhian_Garza
I can only mention 2 people per reply, but since you commented on this thread in the last few months, hoping I can catch you with my note above.