I've caught the same error several times:
1. As admin I remove a task from the current sprint.
2. I put the task back to the backlog and in a few days I delete the task permanently
3. When it is time to close the sprint I can see at the burndown chart that the sprint is not completed fully. And the difference in hours is exactly the time of the removed task.
4. So Jira continues to calculate deleted task and adds its time to the current sprint time at the burn-down chart.
At the start of the sprint your committed hours (or story points) will be cast in stone. Any changes to the sprint including moving an issue out of the sprint after started, will not change the commitment.
what I recommend is to not move issues out of the sprint at all. Rather you should simply leave the task in the to do status and when you close the sprint it will automatically be moved to your backlog. Also, I recommend not deleting tasks. Rather, moved them to Done and set the resolution to "won't do", "cancelled", etc.
@Jack Brickey thank you for your advice. We use them in our workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.