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
Why does a dependency from another team shows turning my feature red on my teams release train board
Hi @Oleg Appassov ,
Features are owned by programs/ARTS, not teams. If a dependency on a feature is at risk or committed to after it is needed, then the feature is at risk for all teams working on the feature.
The Committed By sprint is past/closed and the dependency hasn't been delivered, therefore the dependency and the related feature are red.
The team delivering the dependency could update the committed by sprint to the current sprint, assuming they will complete the work this sprint. That would change the dependency and the feature back to blue (in progress).
Got it, I guess I was hoping it would show that this feature is at risk for the team that has that outstanding dependency not necessarily other teams as well. I saw that it creates multiple features across each teams so I figured it would be smart enough to flag features only for that particular team but from the release train perspective I get it. Thank you Peter