I have an unfinished PBI at the end of my sprint and I am going to need to move it to my next sprint. This presents me with a bit of an issue however, since I need to maintain a history of what occurred in the previous sprint. Moving the PBI out of the sprint totally removes it.
Currently the only way to fix this is to make a copy of my PBI and Tasks, and estimate the PBI at 0 hours. It would be much better if a read only "ghost" PBI remains in my old sprint.
This could possibly be accomplished by adding a right click context option to move the PBI back into my backlog while preserving sprint history. Meaning that I could use this option to move it back into the backlog, or if I needed to I could still move items back the way I could now, which would not leave a history.
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
-
We have written a Java API routine which automates Actuals generation for us, but we are now losing Task History because we move Stories out of the current Sprint when they approach Done in order to optimize Web client response in our large Sprints.
We urgently need a way of preserving Task History re-instated!
Thanks
Mike Brown
ProQuest -
Loading Profile...



EMPLOYEE

