Version Report problem when adding already closed issues

Question

Hi all,

Summary

For a software project, I'm not getting the version report graph rendered as I would expect and need some help

Background

I've recently joined a company that has already been developing software for over a year. I've joined to support SCRUM and planning. They have been tracking their issues in Jira the whole past year. Several hundred issues with estimates have been closed (status = done) and several hundred more are still open.

No Versions were defined yet in this project. So I did, today.

I then retrospectively, added the issues (including the closed ones of up to a year back) to this version. The "Version Progress" accurately updates to about 60% completion (800 story points finished / 700 still to go).

The problem

What I expected when I open the Version Report, is that it includes all historical data. Of each issue, there is known in which sprint it was, when it was created and when it was resolved.

Instead what I see is, all issues 'assigned' to today. Which is not what I would like to see.

On the contrary, the Release Burndown chart does behave normally, taking into account historical sprints.

Can you help?
Does a bulk change help / certain field need to be updated? Let me know.

Bill Sheboy · Answer

That is interesting...

The documentation page indicates the retroactive adding of "done" issues to the version does not change scope, and that is what your chart shows.  It seems a bit more vague on the impact to the "work completed" (light green sections), and your chart seems to indicate it plots them in their appropriate sprints.

To confirm what that chart is actually showing, you may need to submit a support request to Atlassian to ask.

Sorry I could not be of more help on this question.

Robin_6byrad · Answer

Thanks Bill.

What I mean with that Release Burndown 'behaves normally', or differently, is because now that I added closed user stories retrospectively to a version, it does generate historical data like this (unlike the Version Report).

I would like to see the same kind of historical data generation in the Version Report

Bill Sheboy · Answer

Hi @Robin -- Welcome to the Atlassian Community!

I believe the version report is displaying correctly.  Those issues were not in the version in the past, and were only added by you today.  And, if there was a bulk-change ability for "history" then we could no longer rely upon it to be accurate.

When you note that the release burndown does "behave normally", what are you observing?  Would you please post an image of that report also, showing the same release you assigned issues to today?

Kind regards,
Bill