Why is my deleted Ticket not shown in burndown?

[Stevicus]

Hi all, 

We had a ticket as a placeholder for regression testing, when the replacement ticket was added to the sprint, the placeholder ticket was deleted.

However, the points assigned to the placeholder ticket have not been removed from the sprint. Resulting in the burn-down chart being inaccurate. (And showing a rather alarming Spike!) 

Does anyone have any thoughts on how to resolve this? 

Thanks

[Ste Wright]

Hi @Stevicus

It would appear there is an issue in regards to this - see: JSWCLOUD-12020 

The workaround is to remove the issue from the sprint first - then delete it. Not ideal in your scenario but good knowledge for the future.

I would suggest considering both:

• The need for placeholder tickets and...
• The need to delete tickets

Placeholders:

Placeholder tickets suggest that a piece of work was not ready to be in the sprint. If this is the case, your team could either create it during Backlog Refinement / Sprint Planning - or wait until the next sprint when the issue has been created.

The other alternative is to replace the text on the placeholder ticket with the specific tasks to be performed. Not an ideal scenario (particularly if the estimate changes) - but better than removing the issue from the sprint and adding a new one which would show scope removal/addition on the report.

Deletion:

I would advise removing delete altogether from user permissions.

Delete is an absolute - it means in scenarios such as yours there is no going back to make a modification. For issues, we handle "Done" vs "Won't Do" using resolutions instead - so users can close an issue as incomplete or no longer relevant, but we don't lose the data itself.

Ste