Incorrect matching of existing names for new milestone
Bug #1404514 reported by
Lars Helge Øverland
This bug report is a duplicate of:
Bug #581748: 10.10 milestone name corrupted in JS: 10.1.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
For the create new milestone dialog, when the milestone name is checked for duplication, it seems the name is parsed as a number, which causes some seemingly illogical behavior.
Example: For the dhis2 project we have a milestone called "2.2". We now want to create a new milestone called "2.20", which is semantically different from "2.2". When attempting to create the milestone, a validation message is triggered saying "name: The name 2.2 is already used by a milestone in DHIS".
It seems that "2.20" should be handles as-is as text and be permitted as a new milestone name.
To post a comment you must log in.
