Hi Narothnee,
I expect it might take quite some time to generate enough interest on the current “only one team per task” limitation for Workfront to then reconsider it (let alone approve and develop it), but as you are in dire need, I invite you instead consider the following workarounds:
1. Create common “combo teams” (eg “Team A and B”, with the superset of all users from Team A and Team B), which would then allow the As Designed visibility and Team based functionality. There might be a few practical limitations, so I’d suggest you set up a few common examples and follow them through to confirm the benefits warrant the extra work of maintaining combo teams over time (which, by the way, could be automated, if cost justified).
2. Alternatively, create a Teams multi-select dropdown custom parameter with one entry per team, using the Workfront name of each Team as the Label, and the ID of each Team as the Value. To then assert that a particular task is intended to be assigned via the Teams create a team called “multi-team”, optionally, with every user included if that is advantageous enough (eg for “full visibility”) to warrant the duplicate maintenance of the multi-team membership. When such a Task needs to be planned (on a Template, or a Project), multi-select the appropriate options in the Teams dropdown and assign it to the “multi-team” Team. To then assign the appropriate resources, create a Task report that filters for Team = multi-task with columns in the view for the Teams selected the Assignments (to monitor whom among those Teams has been assigned or does self assign). If those two columns are insufficient to mentally decide and monitor coverage, you might also consider further filtering by Team (ie where Teams contains a certain Team) in order to spot (or perhaps even pinpoint, using NOTEXISTS) those Tasks still lacking at least one assignee from a particular Team.
3. Or for another quite different approach, you could also set up one user 1:1 for each Team (eg first name Team, last name Team Name; with the Home Team set to the Team for which such a user is a proxy) and leverage the existing As Designed feature that allows multiple users to be assigned to a Task. Members of each Team could then filter for Tasks assigned to the “user team proxies” of interest to them, and optionally adopt the convention of replacing the appropriate proxy assignment with their own user in the assignment, thereby confirming the transfer of custody (ie “I will work on this, on behalf of my team), and the flip side of then reassigning the proxy back in order to pass it back to their team (and/or “call for backup”)
Regards,
Doug
