Loading Profile...
Pivotal Tracker changes order of user stories in current sprint once you hit start on a user story
Pivotal Tracker changes user story order in my backlog once I hit 'Start.' As a result, I no longer know what is my prioritized backlog. Seems like a critical error to me - I want engineers to be able to prioritize if they have to during the sprint, but since the original priority list is wiped out, can't do that. Again, GetSatisfaction is not letting me choose which product this is about below, another bug.
I’m angry and feel like Pivotal Tracker adds overhead rather than streamlining the process
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.
The company marked this problem solved.
-
Inappropriate?I may be misunderstanding your issue, but I think what you're describing is a feature, not a bug (I can't believe I just typed that and meant it.)
When you Start a story, by definition you are working on that story in the current iteration. It thus jumps from the backlog to the bottom of the current iteration.
If you are starting stories in the order in which they are prioritized in the current and backlog panes, then the story order won't change. If, on the other hand, you are starting a story that has un-started stories above it, the order would be changed, as that is an implicit re-prioritization of that story.
I’m hopeful to have helped
The company says
this solves the problem
-
Inappropriate?THank you for the quick reply.
I start stories that are set in my current sprint and the order within the current sprint changes. EG, I start story listed #4 in current sprint and all of a sudden it jumps to being listed #1 in current sprint. If this is a feature not a bug I am going to use Excel / never hit the Start button... BTW the GetSatisfaction web site keeps having problems like right now I can't scroll back up this page (was in FireFox had to switch to IE where now don’t have that problem)
EMPLOYEE
