Inconsistent treatment of trailing blank in milestone name

[groups@…]

Recipe:

1. Append a blank character to an milestones' name (I know this is stupid - but has happened)
2. Create a new ticket with milestone set to the one with the blank appended

Effects:

• When expanding the tickets "milestone select control" the milestone is listed twice
• In the roadmap view the newly created ticket is not reported for this milestone but all previous tickets (which have been assigned to the "blankless" milestone) appear

It seems that sometimes trailing whitespace is trimmed when it should be always or never

[zak@…]

Thanks for the great software!

Leading whitespace is stripped from milestone names when the milestone is displayed in the context of a select box.

This behaviour allows a milestone like " 25%" to exist in the database, but be rendered as "25%" in the Milestone: select list in the ticket admin interface.

This allows an incorrect milestone to be set for an item.

A single, consistent behaviour would be much appreciated! :)

[groups@…]

This issue becomes more important as we never can prevent the system being users which do not carefully check the milestone names they've entered.

From the roadmaps' point-of-view these tickets get lost

[Christopher Lenz]

The stripping of trailing/leading whitespace is actually an effect of putting the values in the <option></option> elements: the browser will strip the whitespace.

[Christopher Lenz]

Fixed in [2373]. If you already have milestones with names that have leading or trailing whitespace, you'll have to edit and save them.