Carryover stories from last sprint - using for performance analytics indicators.

[Kelly Logan]

I'm looking to track information about the stories that are moved from one completed sprint to the next sprint, which we call carryover and pull this into automated indicators. 

The challenge is how to pull story information from a story that has been moved to a new sprint using this method:

My first strategy is to find the workflow behind this and see if I can interject or modify it to feed a metric entry. I'm thinking I stamp the sprint moved from, points and the other data we'll use for each story. Anyone tried this? Any other ideas?

So far though, I haven't seen anyone else talking about this, so if there's some different language or other reference someone can point me at, please let me know.

[JaeggerLegane]

You could try to create a metric on the story.parent field and then in turn create an indicator on this metric.

[Kelly Logan]

Well, the trick is going to be capturing the metric info based on the action of moving the story from one sprint to the next. That's why I'm thinking my best option would be to tie it to the workflow behind the dialog that does so, or at least understand it enough to trigger from the data changes.

[Kelly Logan]

So, I found the underlying workflow - there are a few layers, but the core is a call to script include method scrumSprint.moveIncompleteRecordsToSprint(selectedSprintId)

The code is in the base scrumSprintAbstract script include and essentially it gets a list of Completed and Cancelled stories in the sprint, does a query for all stories that aren't in that consolidated list and then loops through them one by one to change the sprint value. The full story object is here at this point, so I'm thinking this would be a place to inject a push to the metric to capture the transferred story data. I'm assuming if I create a metric that generates entries I can then manually push to them.

Alternately, since this is a simple process of just changing the sprint value (I was concerned there might be underlying connections and/or data changes). I might be able to work a metric to monitor a story for changes in sprint when the story state is active (Work in progress, Ready for testing, Testing, maybe Draft/Accepted as well?)