Loading Profile...
Dragging from icebox to backlog goes to current iteration
I am trying to drag a story from the icebox to the backlog but it ends up in the current iteration. I can drag it back from the current iteration to the icebox but never to the backlog.
I’m frustrated
5
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 believes this isn't a problem.
The best solution from the company
-
Hi..this is actually on purpose. Think of the current iteration as a view of the top of the backlog. Tracker automatically moves stories from the backlog to the current iteration, until the current iteration "fills up" based on the initial velocity of your project, and story estimates. For example, if your default velocity is 8 points, Tracker will move up to 8 points of stories from the backlog to the current iteration, the rest will stay in the backlog (these will be stories planned for future iterations). As you add more and more stories to the backlog, it will grow, and you will start to see iteration markers.
The company says
this solves the problem
-
Inappropriate?Hi..this is actually on purpose. Think of the current iteration as a view of the top of the backlog. Tracker automatically moves stories from the backlog to the current iteration, until the current iteration "fills up" based on the initial velocity of your project, and story estimates. For example, if your default velocity is 8 points, Tracker will move up to 8 points of stories from the backlog to the current iteration, the rest will stay in the backlog (these will be stories planned for future iterations). As you add more and more stories to the backlog, it will grow, and you will start to see iteration markers.
The company says
this solves the problem
2 Comments Add a comment
This solves the problem
-
I see it now. That's really cool. Thanks for the quick reply. -
I have reported that this is a problem for me as well after the issue was closed. Consider this a vote for "that's annoying". I've been using a Pivotal Tracker for about an hour in order to evaluate it. This is one of the "features" that I find are "too clever". I'd prefer more flexibility in defining my own iterations and what lives in the backlog. Tie my hands and I'll just get frustrated with your tool.
-
Inappropriate?Perhaps this is a place where a little animation could clarify what's going on... perhaps it goes where you drop it, and the bounces into the backlog as it doesn't fit...1 Comment Add a comment
This solves the problem
-
Not really. The issue is not a misunderstanding about where the drop target is located or about "what's going on". The issue is that I want to be able to drop items in the backlog and cannot. As danp points out, this is by design. A better solution (IMHO) is to merge current and backlog as suggested in another issue (http://getsatisfaction.com/pivotal/to...). They really are part of the same list the way that Tracker treats them.
-
Inappropriate?Yeah, agreed on the 'too clever' part. Velocity should be an 'interesting through not mandatory' concept. I'm trying this out for the first time and the obedience I must display to the Gods of Agile is annoying. Projects and stories should be mandatory — the rest is something the rest of us need to warm up to.
Whatever the business logic is that makes it possible, I'd really like to drag from the Icebox to the Backlog. From a UX perspective, it looks totally do-able, so new users will continue to see this as an error and become frustrated.
I’m frustrated
-
-
Inappropriate?Easy hack:
Manually change your Velocity to 10,000 and close the Backlog tab. Now you have a combined list of all Current and Backlog stories, and velocity is essentially turned off as a meaningful feature.
I’m hacky
-
Inappropriate?You should be able to change your %ge to move a job into/out-of the backlog too, while leaving the velocity as is...
Maybe it'd be reasonable to add a button to the top job in backlog to say "I'm going to work extra hard this week" and have the %ge automatically adjusted so the job gets included; and the reverse to remove a job from current?
Seems like that'd make for a better user experience for this -- the software's telling you how hard you have to work to get stuff done; at a cost of making it more complicated to calculate a prediction for future velocity...
Dunno, just thinking outloud...
I’m unsure
-
Inappropriate?I just reported this as a problem. I'll join the "too clever" party. It's very non-obvious what's going on. Myself and a pair partner spent a while trying to figure out what was going on yesterday and gave up on Tracker. Unless a pivotal person had followed up on Twitter I wouldn't have come back.
I’m undecided
-
Inappropriate?i had the same problem...
just visually show that its moving from backlog to current or when the first story is dropped into an empty backlog/current display a warning/explanation
a tutorial (video preferred) would help too
EMPLOYEE
