Moving issue types are causing confusing Sprint reports...

[Chee-Hong Hsia]

Hi,

Does anybody have the following problem with Greenhopper’s Sprint Report?

Reproduction path:

1. Created project X

2. Created a couple of stories (issue type)

3. Created and include x stories in the Sprint.

4. Move a couple of stories to done (not all) and close the Sprint, so that you have a team velocity.

5. Then I move the rest of the unfinished stories to project Y.

6. In project Y, start (include the moved stories in the Sprint) and close the Sprint.

Problem 1: Go to the ‘Report screen’ Greenhopper has included the results of Sprint 1 of both project X AND project Y.

Problem 2: During the Sprint of project Y, if new stories are added in the Sprint and given a complexity, it won’t get added in the final velocity. Greenhopper see it as 0.

Is there a way to fix this?

In our case we constantly move issues from projects…

[Peter Van de Voorde]

Hi Chee-Hong,

A lot changed to how sprints are handled in the latests version of Jira Agile (formely Greenhopper).

I think you are having a similar problem to the one discussed here : https://jira.atlassian.com/browse/GHS-8168

You could also try the solution that's provided in the comments of that link.

I hope it will help you out.

Best regards,

Peter

[Chee-Hong Hsia]

Hi Peter,

We’re currently using version 6.3.3.

“Are you creating these sprints for project X and Y in the same board?”
No, the ‘issue types’ of project X are moved to project Y. The sprint is then created on project Y. For some reason, the sprint history of project X gets included in the Sprint Report of project Y.

“Can you provide a screenshot of the report screen showing the problem?”
I’ve added a screenshot.

Cheers, Chee-Hong

[Peter Van de Voorde]

Hi

Which version of Greenhopper are you currently using?

Are you creating these sprints for project X and Y in the same board?

Can you provide a screenshot of the report screen showing the problem?

Best regards,

Peter