You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a quick question on who can be configured as working a project.
It looks like it is not possible to add multiple teams under "Who works on this?"?
The way we are structured it would be a great advantage to allow multiple teams to be assigned as working any project.
You're right, it's not possible to add multiple teams today. I'm adding your comment as a +1 to work on this feature.
Meanwhile, can you tell me more about your structure? Would love to hear why multiple teams per project is something common to you.
We were trying out this feature also, the reason I would want to add multiple teams to a project is based on communicating and tracking dependency coordination.
There are very few deliveries where a single team can go from start to finish without another team being involved (DBOps, DevOps, Platform, Integrations) teams are probably left off of the most alignment discussions until the delivery is too far down the path to not negatively impact the timeline.
We are trying to use the labels, but similar to using the labels in JIRA - the most success we have achieved is when a few people are maniacally managing the labels/components... Maybe we will have better luck using Teams.
I'm taking over from Eric as Product Manager. While we aren't currently working on this, it's on our list of features to get to. I will circle back with more info once we pick it up.
Love the interest. Thanks