Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,558,864
Community Members
 
Community Events
184
Community Groups

Unable to see Capcaity details of previous sprints in Portfolio

Bhaleeq Ahamed
Bhaleeq Ahamed Sep 03, 2020

Hi All,

It would be great if someone can throw some insights, on below

I am using my Scrum Board fed as input to PLAN in Portfolio. I am unable to see the old Sprints Capacity, whereas I can see only current and Future Capacity data related to Sprints.

 

Thank you

Comment
Watch
Like Be the first to like this
539 views

1 comment

Dave
Dave
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 03, 2020

The main reason for this is that Advanced Roadmaps is considered to be a forward planning tool. When a plan is loaded it only fetches issues that have been resolved recently (the number of days can be configured for each plan, but defaults to 30). This is done in part to reduce the number issues that are loaded because increasing the number issues loaded will have an impact on the plan loading time (and in fact there are limits on how many issues are supported for each plan). 

The best way of reviewing historical sprint information would be to review the reports available for projects (such as sprint report, burn down report, etc)

Regards,

Dave

Like • Bhaleeq Ahamed likes this
Bhaleeq Ahamed
Bhaleeq Ahamed Sep 06, 2020

Thank you so much, @Dave 

Like • Dave likes this
Reply

Comment

Log in or Sign up to comment
Portfolio for Jira
Advanced Roadmaps
TAGS
AUG Leaders

Atlassian Community Events

See all events