View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0023806 | mantisbt | api soap | public | 2018-01-09 17:28 | 2018-01-12 07:52 |
Reporter | mantisiator | Assigned To | |||
Priority | high | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 2.9.0 | ||||
Summary | 0023806: Developer can not close an issue unless "Assign issue" right is given when using the mc_update_issue() function | ||||
Description | Hi,
Further to review , it appears that the function mc_issue_update() calls in 2.9.0: but I could not find the associated issue in the 2.9.0 release note. When giving the "Assign issue" right to the developper, the problem disappears, but I do not see the reason why the Assign issue should block the issue closure. For complementary information:
$g_status_enum_string ='15:submitted,50:assigned,35:underwork,36:underintegration,95:cancelled, | ||||
Tags | No tags attached. | ||||
I did not investigate in details, but the change in mc_issue_api.php you mention was introduced in 2.3.0, not 2.9.0 (see MantisBT master 57104f6b) so this is likely not the root cause of your problem (unless you mixed up versions in your report). The error message you mention is triggered by mci_issue_handler_access_check(), called by mc_issue_update() at line 1207. This bit check was added to fix 0023654 / MantisBT master 00dec0b1 @vboctor can you have a look ? EDIT: bloody source integration links |
|
Hi, |
|