I've just raised another ticket for this, then changed my search term and found this ticket.

@Martin Jopson, the burndown chart is pretty useless for this information, it's far too much work to dig through it to find what's been added (especially if it has no points). Having them included in the sprint report is much more convenient.

pvdissel In the Sprint Burndown chart additional scope if reflected in the line, inspecting the data point will show the scope change.

+1 Completely agree with Kevin.

Also, would be nice if everything added to the sprint is shown seperately in the burn down line. So the report gives a good visual indication of the impact of the added stories.

@sclowes I have attached an example

I like the * to show added issues but it would be better to have an issues added to sprint section so I can export that to the issues navigator.

I agree it would be nice to see a section for issues added to the sprint so you can click "View in Issue Navigator" and just see the Issues added to the sprint. Currently you just get a * and no way to extract this data to the issue navigator.

Hi Shaun,

I haven't probably explained properly.
I meant that there is a separate section in the Sprint Report: Removed issues from the sprint.
But new added tickets just go into Completed/Not Completed sections.

There is no such section as Added issues during the sprint.

Thanks,
Inna

Hi Inna,

Stories added after the sprint started should definitely be displayed in the report. If they're not this is a bug that you could report to https://support.atlassian.com and they could try and diagnose what's going on, perhaps you're on a version of GreenHopper before this was implemented.

Thanks,
Shaun