View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0012887 | mantisbt | api soap | public | 2011-03-30 08:37 | 2013-04-06 08:24 |
Reporter | maschneider | Assigned To | rombert | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 1.2.6 | Fixed in Version | 1.2.6 | ||
Summary | 0012887: mc_issue_get_biggest_id do wrong | ||||
Description | if i call mc_issue_get_biggest_id via soap i want the biggest id back, but i get the latest issue not with the biggest id | ||||
Additional Information | if i look in the code i find: 'sort' => 'date_submitted', correct would be: 'sort' => 'id', | ||||
Tags | No tags attached. | ||||
Thanks for the report. Just to clarify, aren't issue ids allocated in ascending order? If that is the case, the sort conditions would be equivalent. |
|
Yes they generated in ascending order so i was confused as well. But as i test it will sort you the task like last_update try this: view_all_set.php?sort=date_submitted&dir=DESC i dont know if deeper in the system sort by date_submitted will be override |
|
Yup, date_submitted seems to be the date of the last update. This should be fixed. |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
MantisBT: master 826cdd8b 2011-04-11 15:36 Details Diff |
Fix 0012887: mc_issue_get_biggest_id do wrong The internal sorting should be based on id, rather than on date_submitted. |
Affected Issues 0012887 |
|
mod - api/soap/mc_issue_api.php | Diff File | ||
mod - tests/soap/IssueAddTest.php | Diff File | ||
MantisBT: master-1.2.x d90003b4 2011-04-11 15:36 Details Diff |
Fix 0012887: mc_issue_get_biggest_id do wrong The internal sorting should be based on id, rather than on date_submitted. |
Affected Issues 0012887 |
|
mod - tests/soap/IssueAddTest.php | Diff File | ||
mod - api/soap/mc_issue_api.php | Diff File |