Preferred Method of Preserving Stats of Iteration While Moving Incomplete Task to Next Sprint? | Community
Skip to main content
P
ParkeBr
Level 2
February 19, 2020
Question

Preferred Method of Preserving Stats of Iteration While Moving Incomplete Task to Next Sprint?

  • February 19, 2020
  • 2 replies
  • 590 views
It appears that when I finish a sprint time box that the sprint is seen as done in the system without me marking it as done. But if I move an incomplete task to the next sprint, I lose the historical data of card information and stats associated with the card. Is there a recommended solution to preserve close state and stats other than a screenshot? (e.g. Want to see what things we worked on last sprint that we didn't complete even if we finish it in a future sprint. Also want to see closing stats at the end of the sprint.) Parke Brown
    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    P
    PatrickHa4
    Level 2
    February 25, 2020
    My best & inelegant suggestion is creating a suite of Custom Fields to capture data for incomplete Story/Tasks in a completed Sprint. Custom Fields track original Story, Estimate, Percentage completion, and the like. Store all this either manually or auto-magically when a Sprint is marked Complete. Then, copy the Incomplete Stories over to the next Sprint. Seems some details need to be addressed, yet this is overall suggestion. Another, perhaps even more awkward suggestion is to Rename an incomplete Story as "StoryName Part 1" in the Sprint that just ended Add a Story "StoryName Part 2" in the new Sprint, using the same Project & Parent Task used for the original, incomplete, and now renamed Story. Both incomplete-original story and new Story reside in same Project & Task, so they will report together for tracking purposes. Pat Harrell Seed Company
    Edwin_Melgar
    Edwin_Melgar
    Level 4
    January 16, 2025

    This is still very problematic 5 year after this original post.

    Our current workaround is to create a copy of the story to keep in the current sprint and move the original story to the next sprint.  As suggested in the comments above, we also rename the stories so they are not confused as duplicates.  The reason we move the original story is because the story details and any comments added on the story do not copy over.  So in order to keep the data nd history on the record the team is working on, the copy is left in the current sprint.  This is not ideal and adds a lot of overhead to the process.

      Terms & ConditionsAccessibility statement

      Loading footer...