Sprint Burndown Issues

[Andrea Robbins]

I have an issue. We do our Jira reporting (using an app) by having two different statuses one for done (after deployment) and Ready for deploy. The resolution is set to done for the Done status. However, for the sprint burndown to work, I know it has to be in the left most column, but that doesn't happen until it is deployed. However, I want it to burndown when it goes to ready to deploy. I can make this status be under the same done column, but then when the sprint is closed ready to deploy items are still there that I don't want to disappear. Is there any way to have them stay in the next sprint but still be done on the sprint burndown?

[Jack Brickey]

I would consider having two different boards one for your Sprint burndown. And then create a separate board for your deployment.

[AMIT GULATI]

@Andrea Robbins If the stories are not getting deployed, how are you delivering a PSI. It means either you need to have the deployment to lower environment as AC for such stories and deployment to prod can be a different story (in subsequent sprint) OR you need to split (functionally)  the story in a way that you are able to achieve deployment to prod in same sprint.

[Andrea Robbins]

what if the subtask was for deployment. Maybe that one would be separate from the burndown?