Why does a dependency from another team turning my feature red on my teams release train board

[Oleg Appassov]

Why does a dependency from another team shows turning my feature red on my teams release train board

[Peter Jessen · Accepted solution]

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).

Regards,
Peter

[Oleg Appassov]

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

[PACKER, JASON]

Sadly, this remains an open question in 2024 - the system is smart enough to put an instance of the feature on each team's swim lane, but not savvy enough to only mark it as a problem for the team that has the unmet dependency.