Is there any way to capture reasons for stories that are not done when Sprint is completed?

[Ganesh Kumar Vary]

Hi,

This is a typical testcase where we want to capture the reason when ever there are stories still pending when sprint is completed.

Currently, when ever a sprint is completed, the stories that are not done can be moved to either backlog or the next sprint. Now, the requirement is to capture the reason for each story why is was not able to be completed in the sprint.

I have been trying different methods to capture the reason but couldn't do so. Can I know any work around for this please. That would be very helpful even if any plug-in can be used to solve this issue.

Thanks & regards,

Ganesh Kumar 

[Nic Brough -Adaptavist-]

There's no way to do this other than to individually comment on each issue (or maybe have a dedicated custom field to edit), and you'll have to slog through each one individually. 

You'll need to write an app to intercept this and pop a screen to duplicate the reason across all the issues affected, and I'm not sure you can do that on Cloud, I'm not sure you can intercept the end sprint process.

Instead, I would question why this is of any use.  An issue moves into the next sprint because it is not done at the end.  That's all the reason you really need.  Inside the team, you should be doing some retrospective work on looking at why, but the main causes are going to be "we overestimated what we could achieve" or "something interrupted the team, or created a blocker on the story unexpectedly", neither of which need directly recording on issues.

[Bill Sheboy]

Hi @Ganesh Kumar Vary 

Yes, and...to what Nic notes:

When teams build/buy something to solve what should be a short-term symptom (e.g. carrying over work to the next sprint) rather than discuss and experiment to improve the situation, that can make the symptom into "our new normal".  

And so the team no longer feels a need to investigate or solve it.  Consider instead trying to quickly see and address such issues, and share what is learned with other teams.

Kind regards,
Bill

[Jacob Vu]

Hi @Ganesh Kumar Vary

Are you looking for an automated response to explain why an issue wasn't able to finish in said sprint? Is there any reason why you can't write a comment explaining why it wasn't completed?

Jacob

[Ganesh Kumar Vary]

Hi @Jacob Vu,

Thanks for the quick response. The thing we are looking here is for specific stories that are not able to be completed in their specified sprint.

And there requirement from client is very specific that when ever "complete sprint" button is pressed, there should be some sort of a pop-up screen visible (Similar to transition screen) to capture the dropped reason.