View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011280 | mantisbt | api soap | public | 2009-12-10 13:48 | 2012-03-26 06:15 |
Reporter | coyttl | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 1.1.8 | ||||
Summary | 0011280: mc_issue_add function not honoring "date_Submitted" field. | ||||
Description | Possibly related to 0011274, the "date_submitted" field of the IssueData is not honored upon creation of a new incident through the mantisConnect.mc_issue_add(IssueData) call. | ||||
Additional Information | This could be debated whether or not it's an actual 'issue' or not, because people could claim that even thought the "date_submitted" is set to yesterday, it was literally 'created' today during the remote import. I only opened this because, as a developer working on a side-project, I had expected it to be honored, and was surprised that it wasn't. | ||||
Tags | No tags attached. | ||||
On the one hand, this should not be spoofed and she be typically auto-set by MantisBT. However, for scenarios like migration tools, it makes sense to be able to set this and be honored. Hence, I think that we should honor it based on a configurable access level. |
|
Thanks. I'm working on a migration tool, so to myself (and users of the tool), it would be useful. |
|
I'm using this change on 1.2.0 to fix that behavior: diff -r mantisbt-1.2.0/api/soap/mc_issue_api.php mantisbt-1.2.0-wepl/api/soap/mc_issue_api.php
|
|
I'm facing this issue in Mantis BT version 1.2.9. Is there any plan to fix this issue? |
|
It would help if someone can implement this on a fork in github and send a pull request. I would like this feature to be controlled by an access level (migration_access_level or something similar) that is set to ADMINISTRATOR by default. |
|