Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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


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

Screen Shot 2020-02-20 at 12.53.50 PM.png

1 answer

1 accepted

2 votes
Answer accepted
Peter Jessen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 20, 2020 • edited

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

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events