View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015951 | mantisbt | feature | public | 2013-05-30 17:10 | 2013-06-09 06:51 |
| Reporter | cbj4074 | Assigned To | atrol | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | 1.2.11 | ||||
| Summary | 0015951: Numeric releases are ordered incorrectly in Target Version menus | ||||
| Description | Many software release naming conventions use increasingly longer (and more specific) names for subsequent releases within the same major version. For example, 1.0 might be the initial release. And then comes 1.1. And perhaps later, 1.1.1, and eventually, 1.1.2. In Mantis's "Target Version" menus ("Target Version" when editing an Issue, "Update Target Version To menu" when editing multiple Issues, and possibly elsewhere), releases seem not to be ordered with this convention in mind. Per the above example, the displayed order is: 1.1.1 The desired order is: 1.1.2 The Roadmap facility seems to suffer from the same issue; the releases are not sorted in descending order in consideration of this same convention. Is this something that is on the end-user to customize? | ||||
| Tags | No tags attached. | ||||
| duplicate of | 0010419 | acknowledged | Allow customized sorting of versions |
|
Versions are ordered by field "Date Order" Do you agree that I close your issue? |
|
|
I found also the feature request 0010419 which covers also your request. |
|