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!


Portfolio Improved Interface will not use points from stories to estimate sprints, only epic level?

Using the improved interface of Portfolio and trying to map out future sprints based on points from stories.  These do not appear to count against the velocity at all, however if I only add the points on the parent epic the points will be evenly split across sprints.  

Why won't the individual stories' points be counted toward the projected sprint?

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 10, 2019

Hi @Matt Marcus ,

Can you confirm which version of Portfolio that you're using please?

Judging from your description it looks like you're not actually assigning the issue to a sprint. When you group by team and choose to view capacity on the timeline you will see the sprints (if there is a board associated with the team)... it looks like you've reached this point already!

When you assign story levels to sprints (rather than just setting target start and end dates for the sprint) then you will see the capacity changing.

However, when you set the dates for an epic we will actually distribute the story points over the span of sprints that it covers (as you've also discovered). 

Although we made a conscious decision to not distribute the points from story level issues based on target dates, we're actually looking at making some changes to this behaviour to improve the way that capacity is reported. Can I ask that you e-mail us at so that we can discuss this in more detail with you as we're keen to get some feedback on the current behaviour and our proposed changes.

Many thanks,


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events