Getting correct sprint dates in portfolio

[Thomas Okell]

Hi, 

I am currently using JIRA portfolio for a cross-tower release and I have set it up with the boards and a cross-project release but there are a few problems that I am having.

First of all, some of the sprints are not being pulled in correctly from the boards. On Portfolio it is saying the sprint 4.0.6 Dev Sprint will go from 11/Nov/2016 to 25/Nov/2016 but when I view the sprint in the board for the particular project the dates are correct and say from 07/Nov/2016 to 25/Nov/2016. This aligns with the team iteration length that is set in portfolio which is 3 weeks. The capacity of this sprint also does not align with the velocity input in portfolio, I assume this may be due to the shortened sprint length?

image2016-11-10 16:37:39.pngimage2016-11-10 16:40:36.png

Does anyone know why this may be? This only seems to be the case for one of the towers.

Another problem is that some of the sprints for one of the towers are not tagged to the right sprint in portfolio. Below is an example showing a story that in JIRA is tagged to 3.1.9 but in the portfolio it has been tagged to 4.0.0. Does anyone have any understanding of this issue and why it may occur? The sprint that the story is tagged to in JIRA finished a few months ago.

image2016-11-10 16:44:36.png

image2016-11-10 16:45:16.png

I would be grateful for any help.

Thanks,

Tom

[Christian Yang]

Running into this issue as well. Some of our sprints in Portfolio don't match the actual sprint dates and instead is offset to what looks like today's date, causing our whole roadmap to shift over.

[Thomas Okell]

I think this problem is almost solved now and it is just the issue of teams not closing their old sprints

[Thomas Okell]

@Nic Brough [Adaptavist] could you help?