View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023657 | mantisbt | api soap | public | 2017-11-20 10:01 | 2017-12-04 02:17 |
Reporter | mantisiator | Assigned To | atrol | ||
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 2.8.0 | ||||
Target Version | 2.9.0 | Fixed in Version | 2.9.0 | ||
Summary | 0023657: mc_issue_update returns bug is read only on status update | ||||
Description | Hi all, When updating an issue status:
For information, the problem does not happen with an admin account. Extract of the xml file called via curl : ?xml version="1.0" encoding="utf-8"?> | ||||
Tags | No tags attached. | ||||
related to | 0022552 | new | mc_issue_update doesn't honor project "resolved/read only" settings, adjusted threshholds, or "allow reporters to reopen" |
Hi, The problem thatI see while debuggins that while calling the function via the SOAP api, the bug_is_readonly always returns true, since referring to the global parameters g_bug_readonly_status_threshold set to 80 (RESOLVED) and g_update_readonly_bug_threshold set to Manager. Question: How can this fuction call refer to the project specfic values of these parameters (which are taken into account when called via the Web interface and visibly not via the soap API. Thank you very much for your help ! function bug_is_readonly( $p_bug_id ) {
} |
|
Changing function bug_is_readonly
to
should fix the issue. |
|
Hi atrol, Thanks a lot in advance ! |
|
We might uncover other bugs after this bug is fixed.
Let's wait for the PR feedback of other devs. |
|