View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012299 | mantisbt | other | public | 2010-08-26 18:27 | 2010-08-29 11:34 |
Reporter | micahg | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | git trunk | ||||
Summary | 0012299: Target Version sorting on View Issues page should be numeric, not textual | ||||
Description | Example in reproduce steps. | ||||
Steps To Reproduce | Have at least 3 bugs with 3 different versions, one should be numerically larger, but textually smaller: | ||||
Tags | No tags attached. | ||||
Versions are stored as text, not number. You could name your versions like 0.02 , 0.03, ... 0.10 to get what you want |
|
That's fine, that's what PHP's natsort is for: |
|
AFAIK natsort can not be used for ordering in database. IMO sorting after database fetch should not be used because this would lead to performance / memory problems. |
|
Ok. How about sorting the version based on the release date the same way they're shown for the target version? |
|
Ordering by something which you don't see is confusing. Introducing a new column "target_version_date" could avoid this. |
|
The assumption is the developers will organize the releases based on the order of release, hence sorting by date should be a sensible workaround. Also, a simple join can solve the multiple table issue and if necessary, a compound key can be added to mantis_project_version_table for date, version so as to speed up queries. |
|