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
Due to recent challenges of most companies having to move to virtual and remote PI planning events, the Jira Align Solutions Architects wanted to start to capture some best practices and FAQ Table of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events