Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
We recently started using JIRA Portfolio, I imported all epics and stories of our current Scrum board and started experimenting with the automatic planning options of Portfolio.
One thing I noticed immediately is that stories which are already marked as 'Done' (because we finished them before we started using Portfolio) are still included in future sprints. It does not make any sense seeing a story which is already finished being placed in a sprint which will start in 4 weeks. Also, but I am not sure, they prevent other stories which are not done from being planned earlier making the project seem longer than it actually is.
How do I prevent stories which are already finished from being used by JIRA Portfolio?
Hi Mathyn, this is indeed confusing in the way it behaves right now - we are working on an improvement in the current development sprint to mark items as done already upon import based on their issue status, so that they can be included for reporting purposes, but are not planned into future sprints.
Meanwhile, here are the options you have:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs