Associated team is purely a legacy remnant of the previous way teams and projects used to be connected to each other. The “new way” is now by making a team a project member. The key point being the way Asana wants you to visualize it is that teams are now groups of users, not containers for projects. We all need to get used to that change because that’s the current Asana design. Yes, it’s a big conceptual shift but does have its merits for sure.
So no, I would not submit any enhancement requests around Associated Team; based on my conversations with Asanas, I am sure they won’t be doing any more work there.
Personally, I think the new system is good.
Until now, multi-homed tasks were Asana’s greatest feature.
With this specification change, I understand that projects have also become multi-homed.
If that’s the case,
when viewing task details, multiple projects are displayed.
Similarly, when viewing project details, it seems more natural that multiple teams should be displayed, don’t you think?
To reiterate,
My current understanding is:
-A task can belong to multiple projects (up to 20). The projects it belongs to are displayed in the task pane.
-A project can belong to multiple teams (unlimited?). In the project pane, you can set up to belong to one team.
Similar to the relationship between tasks and projects, I would like the project pane to display all the teams a project belongs to. Currently, I’m having trouble figuring out which teams a project is connected to.
@ka_nishiyama, Are you aware that the multiple teams a project is shared with are displayed in the project’s Share dialog?
I sympathize that it’s messy because of the baggage from the old model, but I’m not sure there’s a better UI than what Asana implemented, even though the two types of team relationships with a project don’t appear together. Just my opinion though…
Totally get the benefit of teamless projects, but it now seems that it is actually impossible to create a project on a team without manually adding it after the fact?
I have dashboards built to only report on the projects within a specific team, and now none of the project data is visible for new projects because it’s technically floating and not on a team. Regardless of how I create the new project (if I create from the Team or using a team-based template with team-specific permissions) they are always teamless 100% of the time. Any workaround I’m missing?
Assuming by “on a team” you’re referring to the Associated Team field, then yes, you’re correct that there’s no way other than after the fact (well, there is a way I mention above using our Flowsana integration ).
This is because Asana has moved away from the concept of a project “being on a team” and toward the concept of a team being a member of a project, which you CAN set when creating a project. The “Associated team” is now legacy concept, might or might not stick around in the future from what I hear. (Note: I’m not endorsing this change, I don’t happen to like it as currently designed; just explaining.)
Thanks, Phil, yeah I was looking for a solve that didn’t include adding anything to the tool stack or budget. Was hoping I was just being dense and there was a clear work-around, but alas. I get that we’re being pushed to use Portfolios, but the UX on them is still so clunky that it’s a hard sell for me!
).