I am trying to finalize the group structure by creating a department and group teams, e.g., Operations and Support. Since there is no way to show a hierarchy for teams, we are going to use fields to show the department and teams. Is that overkill?
Thanks!
Hi @Jim_Roberts , welcome to the forum 
Could you clarify where you are going to use these fields and what these fields are? Where do you want to show the hierarchy of your teams?
It is common to create a field called ‘Team’ or ‘Department’ (listing the options of the same Teams that you’ve created in Asana) and use such a field in numerous projects to set the value of the field against a task, beyond the Assignee field.
You would not need such a field in a Portfolio because you can simply show the native ‘Teams’ column from the Options menu. This will show the Teams that ‘own’ the project.
Similarly you would need such a field for Goals because you can use the native ‘Accountable team’ field.
Sure! Thanks for quick reply. I thought having parent/child tag at the task level would greatly expand reporting and filtering capabilities everywhere, but especially at the portfolio level. However, I am concerned that expecting everyone to ensure these fields appear in every task, for every project could be too onerous. Thanks again!
Yes, that could be quite demanding. You could perhaps have rules set values to your ‘team’ field based on the assignee. This rule could be scaled using a Bundle, available on Enterprise.
However, you mentioned tags - I would not use these since they are not supported in Dashboards and reporting.
You may also want to take a look at this post:
Thanks for the detailed response. I think I will ditch the requiring the department and group name for each task. I thought it would help with more control for reporting and visibility at the portfolio level.
Best,
JIm
Thanks so much. I would have considered the emojis, but now I will! And yes, I do have the enterprise plan.
Best,
JIm
Glad to help, @Jim_Roberts !
As I understand, Asana only has the concept of a team. There are no divisions, departments, or sections.
So, how about including the organizational hierarchy in the team name? For example, Machine Tool Division, Large Machine Department, Design Section, Manufacturing Section, Maintenance Section.