How to track how many times a story has been spilled over different sprints

Question

Hello,

Here is one post - How to track how many times a story has been spill...
But couldn't follow the right approach for my requirement-

A story is spilled over, let's say I agree to take it to the next sprint when completing the current sprint. But due to some unexpected reasons, same story is spilling over for continuous multiple sprints. Now, I need to trace that since this story is getting spilled & how many times it has spilled. I expect this information to be updated automatically to avoid any human modification, rest in its logs I can check its work history.

Can someone please suggest if it is not to expect from Jira?
Else, how can I add this data in such stories automatically?

Thanks

Nitin Agrawal_px4mlo · Answer

Hello @Aaron Williams

Thanks for your solution, I added the rule & it got executed successfully but strangely field not getting updated.

As I was not much aware about how the spilled over stories can be tracked, but now I see there is 'Sprint' field which is showing the list of previous sprints & count-

Also, I see 'Label' field showing the last 2 sprints names-

So, I think, I can get my question answered by this only.
But, it was great to learn about automation from your answer which can be used in future.

Nitin Agrawal_px4mlo · Answer

Hello @Aaron Williams

Thanks for your efforts to help me.

I will try to follow what you have written above & will let you know if it works or if any further explanation is required.

Thanks,
Nitin

Aaron Williams · Answer

Hey @Nitin Agrawal

I have something working for you.

I have created a custom field, which is a "label" type, I called it "SST: Previous Sprints"

Here is the basis of the automation:

Trigger: when sprint finishes. (Pick your board)

Branch for each: Issues in sprint

JQL IF: status != "Done" (pick your resolved statuses)

Edit: SST: Previous Sprints (pick your custom field)

In the edit of the custom field you need some JSON too add the new label, without it, it will overwrite old info and only add the new label.

So here, you are copying from the work item, itself. (So all previous labels) And then the JSON adds the new sprint name as a label.

As you can see, this ticket has been in 3 previous sprints.

I really hope this hits the spot for you, with very little overhead.

Let me know if anything needs further explanation. Oh and ignore the yellow triangle in the automation, Jira thinks the JSON is invalid, it isn't.

Thanks

Aaron.