Loading Profile...
The 'move to top of backlog' feature does not behave as expected
We just de-prioritized a release full of features and moved the next two releases up.
I got to use multi-select and an action... woo hoo!
Only problem is, is that the move to top of backlog action does not consider the unstarted stories in the current to be the top of the backlog. So I had to tediously move those stories to their release. ..and, of course, while doing that the velocity caused things to jump around. I've used tracker for a while so I wasn't surprised, but if I was at all new to tracker I would have been utterly confussed and probably stressed out that I had just messed up the entire project. (I didn't)
I really think the current should be the backlog and the there should just be multiple panels that show the backlog. Current is just the backlog right.
So in the meantime 'move to top of backlog' should move to the top of unstarted stories in the current iteration.
I got to use multi-select and an action... woo hoo!
Only problem is, is that the move to top of backlog action does not consider the unstarted stories in the current to be the top of the backlog. So I had to tediously move those stories to their release. ..and, of course, while doing that the velocity caused things to jump around. I've used tracker for a while so I wasn't surprised, but if I was at all new to tracker I would have been utterly confussed and probably stressed out that I had just messed up the entire project. (I didn't)
I really think the current should be the backlog and the there should just be multiple panels that show the backlog. Current is just the backlog right.
So in the meantime 'move to top of backlog' should move to the top of unstarted stories in the current iteration.
I’m not as impressed as I wanted to be by new features, but I'm still glad they are there.
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?Sorry we didn't reply earlier....you're right, move to the top of the backlog should really move to the top of all unstarted stories (in backlog and/or current). We'll add a bug for that.
Also, in the next release, it will be possible to include the current iteration in the backlog, as a view option. We hope to have that rolled out by next week. -
-
Inappropriate?This is awesome!!!
BUT it doesn't seem to remember what I like, so I rarely use it...
because of this, I doesn't address the unexpected behavior of moving selected stories to the top of the backlog when the panels are separate (unexpectedly, the stories only move to the top of the 'backlog panel' and not the top of the backlog).
...and if I do combine the panels it only moves those stories up to the top of the next iteration.
I think you guys might want to either change the name of the action from "move to top of backlog" or change the what the action does so it behaves as expected. I hope you change the behavior and also add some memory (per project) around my preference for keeping the backlog and current iteration in one panel.
I’m thankful but a tiny bit disappointed
-
Inappropriate?Tracker should remember whether you want to include current in the backlog, but you have to tell it to (View - Autosave Layout). For the other issue, we're changing the 'move to top of backlog' feature to always move selected stories to the top of the unstarted group.
EMPLOYEE
