Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why does Program Allocation report show the same number for both points planned and points accepted? Edited

I have 8 teams in total and they are all showing up on the program allocation report. Unfortunately for each of the last 5 sprints for everyone of my 8 teams, the points planned shows the same as my points accepted.

Is this how its supposed to work? Is this how it works for all of the users? If so what's the point? I would expect that it show the points planned and points accepted similar to how it shows in Jira velocity chart. Currently the points accepted corresponds to that in Jira. But the points planned is the same as the points accepted. And No... All the 8 teams  did not complete all the stories that they took in exactly over the period of 6 sprints!!!

Any ideas?

1 answer

1 vote
Tom O_Connor Atlassian Team May 25, 2021

@Jay Michael the simple answer is because your Avg Team Velocity is 0.  The Avg Team Velocity is calculated on the last 5 CLOSED Sprints.  If the Sprints are not closed, then you will not get a team velocity.

The more complex answer is how this report is using data from Jira and the sprint information that comes over through the integration.   Let's say the team planned 25 story points of work for the sprint, but only accepted 20 story points.  The report should be 25 planned and 20 accepted.  In Jira when you close the sprint and move the incomplete stories to another sprint (versus pushing it to the backlog first), the planned points that Jira sends for the current sprint to JA is 20.  So now the report shows 20 planned and 20 accepted.  

There are some other views such as backlog sprint view and the team coaching report that may show planned story points at the beginning of the iteration.  We are having conversations internally on how to best use this type of report and the data that drives it.  

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Align

Helpful hints if you're rolling Align out to your entire enterprise

(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...

1,360 views 3 28
Read article

Community Events

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

Events near you