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,298,691
Community Members
 
Community Events
165
Community Groups

How does one enter historical data into Jira Portfolio?

I have my plan going forwards from the current spring onwards.  The actual product development started 3 sprints ago and I am keen to enter these three historical sprints.   I just tried the most recent sprint first.  

I entered the custom spring for each team.  

I then imported the relevant stories all of which were children of existing and current Epics.  This showed these completed stories in each Epic without a Release, Team or Sprint allocated.  

I then set the earliest start date for all the items in the current sprint to the first day of the current sprint to prevent them being allocated to the historical sprint that had capacity.

I then changed to current release to start from the beginning of the historical sprint.

For each completed story, I allocated the Release, Team and Sprint; this all seemed to work and the Backlog looked fine.

However, when I display the schedule, the completed stories allocated to the historical team sprints do not appear in the display.  The historical sprints show nothing allocated and have full capacity.

I have tried all sorts of things to try and get Portfolio to recognise these items in the Schedules displays but with no success.

How can I get Portfolio to display the historical information correctly?

1 answer

0 votes

I replied on your support case, but I'll paste the response here in case anyone else stumbles across this question:

JIRA Portfolio never displays historical stories in the schedule once backlog items are marked as complete. The graphical schedule is forward looking only, the backlog table is the only place that you can see those historical stories.

We've got a feature request open that's similar to the request you're asking for, the ID is [JPO-386|https://jira.atlassian.com/browse/JPO-386]. Please do vote on it, and if you can comment with your use case that will help our PMs when implementing the changes.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

219 views 1 4
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