Loading Profile...
Stories getting all out of order
I've noticed since the recent downtime that my stories get all out of order. finished stories in green even go back to the backlog sometimes. stories above one release are now above a different release.
this is a pretty major problem for me.
this is a pretty major problem for me.
I’m frustrated
2
people have 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.
The company marked this problem solved.
-
Inappropriate?We're looking into this, thanks for letting us know.
-
Inappropriate?Hi Justin,
We deployed a fix tonight that should keep this from happening again. If you send your project name to tracker@pivotallabs.com we can run a script to fix your current story order.
Sorry for your trouble and thanks again for letting us know. -
Inappropriate?Even though this is marked as solved, I started having this problem today. -
Inappropriate?Hi Hanno...I assume this project looked ok until now? Do you happen to remember what you did in the project before the accepted stories started to appear in the backlog?
-
Inappropriate?Hi danp,
I just started the project about a week ago and everything looked fine until yesterday. I can't say what I was doing exactly, but the problem is showing up consistently since I first noticed it. Here's what happens in more detail:
- I open the project.
- Some or all of my stories from the last iteration show up in the current iteration because unfinished stories are in front of them.
- All my finished stories from the current iteration show up in the backlog (next week's iteration). Again, stories from the backlog have moved in front of them.
- I reorder all the stories as they were. Everything looks fine.
- I do anything that causes the story page to reload (hit reload, go to the dashboard and come back, ...) and the stories are all messed up again.
Here are some patterns that I noticed:
- There is some variation in the messed up ordering. For example, one time one of the three stories from last weeks operation stays in its correct place. After I reorder and hit reload it is also mixed into the current iteration.
- That said, I can't observe a variation right now. It always looks the same now after I reorder and hit reload, but I'm a 100% sure that the messed up ordering was different when I started writing this a few minutes ago.
- Finished stories seem to maintain their ordering to each other, as do unfinished stories. It's just that the two groups are mixed.
- Finished stories of the same type seem to stick together. For example, all the finished stories from my current iteration are chores. So far, I have not seen them separated.
For clarification, here's the correct order:
And what it looks like after I hit reload:
As I said, I can't remember what exactly I did that could have caused this. My last activity on the activity feed was creating a chore that I later moved to the top of the queue.
I hope this helps.
edit: Replaced the images with smaller images, cutting away the irrelevant stuff.1 Comment
Add a comment
This solves the problem
-
Hi Hanno,
The bug was fixed, but it did leave a limited number of projects (mostly projects that were created between January 23rd and 25th) with some stories with the incorrect priority. The incorrect priority may not manifest itself until later point when some other user actions are taken. I ran a script to fix your project's story order. Your story order may not be perfect since we did lose some information about priority, but accepted stories are now before unaccepted stories etc... Sorry for any inconvenience that this may have caused you and let us know if you have any other questions or problems. -
Inappropriate?Thanks a lot, everything is back to normal.
Don't worry about the inconvenience. I don't have a lot of stories yet and last time I looked I was using this for free anyway ;)
Again, thank you for resolving this so fast!
I’m happy the problem was resolved
EMPLOYEE
EMPLOYEE
