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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,764
Community Members
 
Community Events
176
Community Groups

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

Edited

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

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

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
TAGS

Atlassian Community Events