Specifically, I asked my scrum master to add some already completed JIRA issues into a fix-version to more accurately reflect the work completed and the work yet to complete so it's reflected in the version report. As expected, as soon as they were added, the version report showed them as completed on the date they were added.
How do we adjust the 'closing date (?) of the completed issues so they don't skew the version report?
Hi @Chris Mitchell and welcome to the Community!
Short answer: don't.
You seem to have just discovered how you can use releases manage versions. In practice, this is just the set of features you release together. A release (or version) itself has a start and release date. And basically all the issues you add to that release (with the release's start and end date) have supposedly gone live in that release.
You may have found out that you cannot release a version (i.e. close that release) while there are incomplete issues still in it. If you still want to release that version, you'll need to reassign open issues to another version. So in the end, all issues in a completed release will end up being closed and the only date that matters at that point is the release that of the version itself, not when the individual issues were completed.
The close date of the issues (resolved when you look at the issue's fields) is a system date that gets set automatically. You could reopen all your closed issues (clearing the resolution) and then close them again, but that seems like potentially a lot of work for really no other added value than manipulating a report that you seem to have just discovered. Going forward, you will not have any issues with this in upcoming versions once you are in a proper cadence.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.