Changing a ticket's story point value between sprints

George_Hobbs

I've just closed my team's sprint, and a ticket worth five story points has not been completed, so it has spilt over into the next sprint (by default).

 

The problem is that this ticket is 80% complete, so rather than it commanding five SP in the new sprint, I want it to only be worth one SP (20% of original estimate).

Is there a way to log that 80% of a task was completed in one sprint, and flexibly change the SP value of the ticket for the new sprint, to reflect that the task is almost complete?

Thanks

Stephen Sifers

Hello George,

Jira will handle any uncompleted issues by spilling them into the next sprint (as you explained above). An issue with 80% completion (while work has been done on the issue during the previous sprint) is still considered not complete. Only issues with 100% completion as considered complete.

An un-ideal work around for this would be to Reopen your sprint (Modern versions of Jira and Jira Cloud). From there you can adjust your story points AND take the remaining 20% left and create a new issue for the next sprint (spilling the remaining story points over into this issue). This will allow you to track completed work in the closed sprint along with splitting your story points between the issues. However, this may impact your reporting as your original sprint completion date will be impacted since it will be reopened and then completed.

Here is the guide on Reopening a Sprint: 

Cloud: https://confluence.atlassian.com/jirasoftwarecloud/reopening-a-sprint-785332001.html

Server: https://confluence.atlassian.com/jirasoftwareserver/reopening-a-sprint-938845456.html

Along with this we have a Jira Software tutorial for Sprints within Jira (Including as additional information for others): https://www.atlassian.com/agile/tutorials/sprints

 

-Stephen Sifers