Just a note that in most other contexts, disabled schedule objects are all-but-invisible. For instance you cannot target a bug to a disabled milestone unless you first reenable the milestone. So there is a kind of consistency argument, beyond just usability, for hiding the disabled ones.
Just a note that in most other contexts, disabled schedule objects are all-but-invisible. For instance you cannot target a bug to a disabled milestone unless you first reenable the milestone. So there is a kind of consistency argument, beyond just usability, for hiding the disabled ones.