Increasing the 15 dependency limit

Hey friends,

Converting this discussion thread into Product Feedback.

I’ve been using Asana as the front-end for a complex program plan with 300+ tasks. I maintain the database of tasks, durations, and dependencies (plus other custom fields) separately where I can do analysis and automatically remove slack.

I then programmatically update Asana through the API and use it during meetings to discuss with project leaders and get their comments. With the exception of the timeline loading issue, people like the interface.

Recently, I’ve started getting API errors when assigning dependencies. It looks like it’s because some central milestones had accumulated >15 dependencies and I understand this is a limit. I can work around this using artificial sub-milestones, but that’s confusing to the users and is more work for me.

If it’s not something totally fundamental to your architecture, can we increase the limit to at least 30 to accommodate large/complex projects like mine?

Thanks!
Wes

Thanks for creating this request, @Wes! We currently don’t have immediate plans to he 15 dependency limit but I’ll make sure to share this feedback in our next Voice of the Customer meetings with the product team so they can consider it in future updates!

We just hit the 30 dependency limit in one of our templates. It would be great if it was possible to adjust that limitation upwards a bit.

Thanks!