Milestone dropdown incorrectly initialized
It looks like tickets that have not yet been assigned to a milestone have a problem when being edited: the Milestone dropdown defaults to the earliest milestone, instead of defaulting to "None," as many would expect. Is this intentional?
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Colin Bartolome on 08 Jun, 2009 04:40 PM
A co-worker now says that she can't select the "None" milestone at all. Is it being phased out?
2 Posted by Rick on 09 Jun, 2009 07:00 PM
Nope, this was a bug that someone committed. It's been reverted.
3 Posted by Colin Bartolome on 15 Jun, 2009 05:00 PM
This has also become a problem with the "Who's responsible?" dropdown. I keep clearing it on various tickets, but it keeps defaulting to the first user in the list when other people come in to make a comment.
4 Posted by Nicole on 10 Aug, 2009 05:21 PM
Hi Colin -
If you're still experiencing this problem please respond to this discussion and we'll take a look at things again.
Thanks,
Nicole
Nicole closed this discussion on 10 Aug, 2009 05:21 PM.
Colin Bartolome re-opened this discussion on 10 Aug, 2009 05:25 PM
5 Posted by Colin Bartolome on 10 Aug, 2009 05:25 PM
The "Who's responsible?" dropdown still exhibits the above behavior.
6 Posted by System on 10 Aug, 2009 05:36 PM
A Lighthouse ticket was created for this discussion
Nicole closed this discussion on 18 Feb, 2010 06:40 PM.