Loading Profile...
Current stories not moving to done.
We have stories in the accepted state but when the iteration ends they continue to stay in the current iteration (which then gets far too big).
For example we had a story completed 10/1/09. Our iteration starts on Thursday so the break point is 10/14 or 10/15. Today is 10/16/ and the story remains in our current panel.
For example we had a story completed 10/1/09. Our iteration starts on Thursday so the break point is 10/14 or 10/15. Today is 10/16/ and the story remains in our current panel.
I’m happy
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Do you happen to have a release that needs to be finished at the top of Current?
-
Inappropriate?I've got 27 items that are completed which belong in the last iteration. They are hanging around and cluttering up this release (and very much annoying my developers). This is not the first time it happened.
If pivotal doesn't automatically clear them out how can I move them to the done track? -
Inappropriate?Mark,
Pivotal Tracker will automatically move stories accepted in the previous iteration to the done panel as long as all of the stories are accepted and all of the releases are finished. Unless of course there is some bug that needs to be addressed. If you send the project id and name to tracker@pivotallabs.com and we'll look into why those 27 stories are not moving into the previous iteration. -
Inappropriate?I think I see the problem. Not all stories were completed. What happens then?
From my perspective the ones completed should move into the done stage, and those not completed should return to the top or the backlog or remain at the top of current since they will be moved into the next iteration.
It sounds like the assumption is the iteration doesn't complete until and unless all stories in the iteration are accepted. In our methodology, since we don't release every iteration, accepted stories should count as what was completed for that iteration and unaccepted (or otherwise not complete) stories should move into the next iteration.
It sounds like giving users and/or admins the ability to override this functionality and move stores into done would solve a lot of issues. -
Inappropriate?I guess first what is your definition of complete? When a story is finished or accepted? When an iteration rolls over, all accepted stories should roll over to the previous release in the Done panel and only the stories that weren't accepted as well as new stories that fit into the current iteration based on your project's velocity should remain in the Current panel.
If when you say completed you mean accepted, then what you're describing seems like a bug not expected behavior. Again if you'd like us to see if your project is working as expected, please send your project id and name to tracker@pivotallabs.com. -
Inappropriate?Good question. :-)
"Complete" means a story is accepted, i.e. someone clicked the "Accept" button or moved it into the "Accepted" state. I believe this is when it's shown as green in pivotal.
I'll email you the info.
EMPLOYEE
