#5896 Milestone drop-down too large

v1.0.0
closed
Dave Brondsema
sf-1 (616)
General
Cory Johns
2015-08-20
2013-02-27
Cory Johns
No

With the addition of all closed milestones in [#2125], the milestone drop-down is now huge and unmanageable. At the very least, it should use <optgroup> to separate open / closed milestones (with open at the top).

Unfortunately, it uses EasyWidgets, which doesn't support <optgroup>

Related

Tickets: #2125

Discussion

  • Cory Johns - 2013-03-01
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1 +1,3 @@
-With the addition of all closed milestones, the milestone drop-down is now huge and unmanageable.  At the very least, it should use &lt;optgroup&gt; to separate open / closed milestones (with open at the top).
+With the addition of all closed milestones in [#2125], the milestone drop-down is now huge and unmanageable.  At the very least, it should use &lt;optgroup&gt; to separate open / closed milestones (with open at the top).
+
+Unfortunately, it uses EasyWidgets, which doesn't support &lt;optgroup&gt;
    • size: 1 --> 2
     

    Related

    Tickets: #2125

  • Cory Johns - 2013-03-01
    • milestone: forge-mar-08 --> forge-backlog
     

  • Anonymous - 2013-03-04

    Originally by: earnie

    I would prefer to see only the previous closed group in an edited ticket; i.e. not all of them. A new ticket should never see a closed milestone.

     

  • Dave Brondsema

    Dave Brondsema - 2013-03-04

    I occasionally (but rarely) find it useful to move an existing ticket into a different closed milestone.

    I agree on a new ticket, only open milestones need to be shown.

     

  • Anonymous - 2013-03-04

    Originally by: earnie

    I suppose then a configuration option to show 1 or many should be created. That option requires only a true/false checkbox in answer to "Show all closed milestones in Edit mode?".

     

  • Kyle Adams - 2013-03-04

    The SF team has two "previously closed" milestones at a time: one for the forge team and one for the dir team. I'm inclined to err on the side of flexibility here.

     

  • Dave Brondsema

    Dave Brondsema - 2013-03-06
    • summary: Milestone drop-down should use <optgroup> --> Milestone drop-down too large</optgroup>
    • status: open --> code-review
    • assigned_to: Dave Brondsema
    • size: 2 --> 1
    • milestone: forge-backlog --> forge-mar-08
     

  • Dave Brondsema

    Dave Brondsema - 2013-03-06

    I was looking into this to see if there was an easy fix at least for new tickets to only show open milestones. I ended up finding a bug in the original implementation which now fixed will only show the single closed milestone that a ticket is currently filed under. It won't show all the closed milestones, which was an accidental result of the bug and doesn't seem like anybody wants that functionality much anyway.

    allura:db/5896

     

  • Cory Johns - 2013-03-06
    • status: code-review --> closed
     

  • Anonymous - 2013-03-07

    Originally by: earnie

    Thanks for the fast turnaround on this issue.

     

  • Cory Johns - 2013-03-07
    • qa: Cory Johns
     

Log in to post a comment.