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,463,682
Community Members
 
Community Events
176
Community Groups

Why aren't all sprints showing in the Dependency Committed By drop down?

The "depends on" has 6 sprints but only 4 of them are showing in the drop drown.  Does anyone know where the values in this drop down are sourced from?

 

image.png

2 answers

2 accepted

1 vote
Answer accepted

I'm going to take a wild guess and say that BA Operations & Mining does not have those Sprints yet in Jira Align.  If you are syncing Sprints from Jira, check their Jira Board.  If they do not exist then create them.

If the Sprints do exist in Jira, you may need to have your Jira Align Admin check the sprint mappings for errors ...for example the dates may not be close enough the anchor sprints created in the Program Increment.

1 vote
Answer accepted

Hello Kurt,

One of the following could cause this:

  1. When the "Depends on" team has not created all the Sprints on their board in Jira, or
  2. If the "Depends on' team has created the Sprints in Jira, they are not getting synchronized into Jira Align due to some errors.

If you don't have Jira Align Super Admin privileges, then I would suggest:

1) Check the Jira Board for the "Depends on" team to make sure that all the Sprints have indeed been created.

2) If the Sprints exist on the Jira Board, then set your configuration to the "Depends on" team on the configuration bar, and set the Program Increment to the current PI. Then go to the Iterations Grid to see which iterations/sprints exist for the team.  You can get to the Iteration/Sprint Grid by selecting Team --> [MANAGE] Iterations/Sprints.

3) If you see that there are iterations / sprints missing in Jira Align for the "Depends on" team, then alert your Jira Align administrator that some of the sprints from Jira are not syncing for that team.

As a Jira Align administrator, you would have to look at the Administration -> Jira Management to troubleshoot why the Sprints are not getting synchronized.

I found out what was causing our problem.

Go to Team on the left blue menu then pull up Iterations...

Make sure the Iteration is correct in the Sync Date - it must match the actual Iteration - i.e. the Iteration is Sprint 5.  Sprint 5 has to be selected in the Sync Date.

Once I made this change the iterations began to appear in the Committed By drop down...

Like Samit Mehta _321 Gang_ likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events