Can't create a milestone named 0.10 if 0.1 exist

Bug #730367 reported by Matt Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

For some reason it chops the ending zeros off milestone names. So it thinks 0.1 and 0.10 are the same. It should not be doing this.

Revision history for this message
Matt Jones (workhorsy) wrote :

Here is a screen cap to demonstrate the problem.

Revision history for this message
Robert Collins (lifeless) wrote :

This might be a dupe, but I don't trivially see it.

Changed in launchpad:
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.