We are using Jira portfolio server 3.11 and have the following issue:
1) Sometimes stories are not finished at the end of the sprint because the work is not finished or the solution is not accepted. These stories move to the next sprint after sprint closure. The particular unfinished story has then two sprints mentioned: the previous and the current sprint.
2) when we afterwards update the plan in portfolio (auto-schedule in the new interface or calculate in the old one) portfolio only sees one sprint, the one that is first mentioned (previous sprint). Consequently, no impact is seen in the portfolio plan that actually the story is moved to one sprint later. I would at least expect that portfolio gives a warning that the date has changed or (even better) that the expected end date is now according to the current sprint.
It looks a bit strange to me that a tool such as Portfolio does not update the planning when the story is moved to a sprint later. Though the only way I managed to workaround, was to create a new plan in portfolio. With so many teams this is a bit a hassle.
Anything that I am missing? What is the best way to update the sprint of a story in Portfolio?
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
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