2

We have marked the Undecided milestone as unassignable, but cases can still be assigned to it. Imo this is a bug since at this point FB does not work as expected.

I can see that for system generated cases (eg receiving email) a default milestone is necessary and that Undecided serves this purpose. But I would rather have the ability to specify my own default milestone.

Fog Creek Case FC1838021

flag

3 Answers

4

The Undecided milestone is built-in. Either it should be impossible to make it unassignable or it should disappear if it's not assignable, so yes, either way, there's a bug and something that needs to be decided here. I'm marking this status-evaluate for the FogBugz program manager to come look at this.

link|flag
Great! I vote for the latter, Undecided is useful in some project types but not in others. Thus being able to enable or disable it would be perfect. – Peter Dec 31 2009 at 12:09
4

It's definitely a bug that an unassignable milestone is assignable. The right solution is probably to make "Undecided" permanently "assignable." Case filed.

link|flag
1 
 It also happens on the quick "Add Case" link on the list case view. Since you can only enter a title in this spot it is defaulting to Undecided, which I've marked as unassignable and deleted so that it doesn't get used. If Undecided was correctly sorted as per fogbugz.stackexchange.com/questions/3930/… I wouldn't care so much. – Barrie Treloar Jul 30 at 7:28
0

I still the same issue in Fogbugz version 8.6. When is this proposed to be fixed?

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.