Loading Profile...
Twitter,
Facebook, or email.
So this project I'm working on has "Bugs and Chores May Be Given Points" enabled but I want to disable it. I started to go through and unestimate bugs and chores, but when I try to save one that is already accepted and in a past iteration, it won't let me save it.
Effectively, it's not possible to unestimate those stories without moving them out of the past, removing their accepted timestamp, etc.
I know we're sinners, but please help us! We want to right our ways! ;)
I’m
distraught
Disabling "Bugs and Chores May Be Given Points" Impossible Without Destroying History
-
You could hax this by exporting all your stories to a new project. Might need some text editing in between, but should be easy enoughComment -
-
I’m
undecided
I don't know if this is a server-side validation in addition to the client-side so I'm going to see if I can use the API to update it.
I'd rather not do a little export/import dance with the data. -
-
I’m
frustrated
Did the API work, or has there been any word on this? It's ridiculous that the documentation says, "Once you have turned this option on, it can only be turned off again if ALL bugs and chores are un-estimated (even ones which are in the done state)." And yet that is not actually possible to do.
-
-
I’m
frustrated
This is really frustrating. Done Bugs can't be un-estimated. You could change them all to 0-point features, but that is extremely laborious. I haven't looked at the API yet, but I feel like I really shouldn't have to.
-
-
I’m
frustrated
+1. This does not work as expected and there's no way to undo it. I now have to estimate all chores AND bugs before starting them. And there's no way to turn this off, even though the documentation says there is.
-
-
1Bugs should be fixed, but guys - A text export -> find/replace -> import would take you less than 10 minutes.
-
-
I’m
frustrated
Hi Joel,
Interesting suggestion but it doesn't work.
Just as you can't manually set the estimate of an accepted chore to "unestimated", you can import an unestimated chore either. Pivotal gives an error message.
Again, once you select this option, there's no way to go back. The documentation says otherwise. -
-
I’m
frustrated
i'm having this problem too :(
-
-
1Once I realized how easy it is to set a chore to zero points by clicking on the bar icons, this stopped bothering me. It takes very little time.
Still, the warning about turning this feature on should be changed. The warning basically says "we think it's a bad agile practice, so don't do it". That's a little condescending because it's up to the user to decide.
The warning should say "this can't be turned off, ever, and you'll need to estimate everything from now on." That message is not conveyed. -
-
-
-
I’m
frustrated
I deeply agree here...
there MUST be a way to disable a checkbox, otherwise, you just need to ask to make the choice at project creation, with a warning, and never after...
We're having our main project stuck here without any way to roll back... -
-
I’m
concerned
Seriously? I'm on my 2nd day of the 60-day trial and was about to enable this option, but I'm glad I read this first.
I find it strange altogether that I can't manually choose to estimate a bug's complexity with or without an option like that. I can appreciate that it might affect a lot of other features and require other changes, but it's surprising to not even see an official response indicating as much.
A year seems too long for an issue like this to not be solved... Is Pivotal Tracker still under development or what?-
PT is still in development, just like Facebook and Google.. It's a live service that keeps getting better, that's why I like it
-
-
Good to hear =)
-
-
-
-
CHAMP
