>... >>> The milestone field should be optional by default. If anything, you >>> might have a plugin installed that's making it otherwise. >> >> I think you misunderstand the problem. I seem to have the same >> problem. It's not that you have to assign a milestone when creating >> a ticket its that you can't remove the milestone later without >> reassigning to another milestone. > > Just based on what I'm seeing in the code, it shouldn't make a > difference whether or not a milestone has already been assigned to a > ticket. If a field is optional it will always display the empty > option. Now, that doesn't mean you're not still having problem. I > just wonder if there's a plugin that's causing it. That or there's > something I'm not seeing in the code, but I don't see anything in > Trac that would cause the milestone field to not be optional.
Aha! Hiding at the top of the Milestone drop down there is an empty/blank item! It looked like decoration and I honestly never tried to select it. Thanks for the pointer. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
