Recently introduced the Enterprise version to our organization and am in the process of building out a template with our trainer. We’re a medium size org that has 30 consistent stakeholders on each project and expect that to grow as we expand our footprint.
I’ve hit a maximum number (20) of project roles that can be added into the template, which leaves 10 stakeholders unable to be assigned to their task sections.
Our trainer wasn’t aware of this. Our account executive never mentioned any maximum quantities across the Enterprise interface. In fact, a key metric in deciding to go with Asana vs the competition was the ability to use Project Roles in a template.
I submitted a ticket to Asana support and got the generic response that they’ll pass it along to the Product Team.
What else would you suggest to have Asana motivate around this?
Yes, our use case is essentially a construction development project, within a program. Several (10-20) projects being managed with static tasks and milestones.
I’m getting the project template established with the team. Standard project roles project over project with same tasks project over project. The variable will be the actual individual performing them.
As we grow, each functional role that faces these projects will need more head count to cover the geography.
So the template will establish a new project, and then my team will update the actual stakeholders according to where that project sits and which construction managers, area managers etc are on it.
That is unfortunate. Tagging @Forum-team to check if there are any plans to increase this limit.
A possible workaround:
Use a custom field to indicate project role (I’d make this a library field so you can use this to search multiple projects)
Match the field values with the project roles for each task
Fill the remaining 10 project roles using the custom fields
– sort or filter by custom field
– fill assignee multi-selecting tasks
It’s not ideal but it is good practice to have that field anyway, because it will allow you to easily re-assign tasks based on project role.
If it is the same task that is being executed by multiple people then you might want to utilise Asana’s ability to assign duplicate tasks to an entire team: See Understanding Tasks > Task Assignee > Assign duplicate tasks.
Because of the limitation with the Roles feature that you only have one chance to assign all roles at the time of project instantiation from the template or else the tasks go unassigned and the role is removed, I often recommend using a “Role” custom field (as JR mentioned) exclusively.