Proper way to release after a sprint?

This has probably been asked a billion times, but I couldn't find a topic immediately.

We just finished our first sprint using greenhopper. I released it and moved unfinished tasks over to a new version. When I go back to the release chart for the first sprint, it burns down from the number of story points we actually completed rather than what we had planned for that sprint (e.g. we planned for 100 points but only did 50. As the sprint was going on, the burndown chart started from 100. Now that is has been released, it starts from 50).

The result is that we lose the record of what we had planned versus what we actually did.

Is this how the software works? Am I doing something wrong? The goal is to look at the record over the last few sprints to refine our estimating.

Hi Tenuki,

There is actually a build-in feature in GreenHopper that will allow you to release your Sprints. In every fixVersion boxes in the right hand side column of the planning board you will find a release button. (The version needs to be selected)

If you click on the button, GH will launch the release mechanism.
This one will find all "undone" issues and ask you if you wish to:
1) Ignore the undone issues and release the version
2) Swap all undone issues to another specific fixVersion and release the version

~By undone issues we are talking about issues that did not reach the last column of the TaskBoard.~

Note that using this button will save your current version charts on your server. We call them snapshots. They will all be accessible from the released chart board at anytime.
Also if you choose to swap the issues the snapshot will be saved "BEFORE" swapping the issues so you do not loose any data on how the Sprint went.

Let me know if this answers your concern.

Cheers,
JC

JC,

I created a test project to try this out and i am still having the same problem(?). I click the release button, it asks me if I want to migrate issues to a new version (I do), and it tells me it is taking a snapshot of charts.

It moves the issues just fine, but the snapshots it creates of the previous version are not what I expect. As mentioned above, they start at 50 and burn down completely -- obviously excluding any data about unfinished tasks. I had expected it to start at 100 and burn down to 50, as it does while you are still in the sprint and have not released the version.

Are you applying any filters in your context?
The charts will be saved based on your context and preferences.

I have not messed with any filter or context stuff. I'm using Default context

Can you check if the default context uses a filter?
If not I suggest that you enter a support ticket at http://support/atlassian.com

Cheers,
JC