Actions
Defect #10233
open
"update issue" silently ignores "status" field if the user is not part of the project, but changes other fields
Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
REST API
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Affected version:
Description
this is very inconsistent:
if a user is not assigned to some project, he still can execute "update issue" requests through REST API (I'm using Redmine Java API for that) and change fields like "summary", but the server silently ignores "status ID" field in this case.
once you assign the user to be "developer" in the project, he can update the "issue status" field as well.
REST API should NOT silently ignore some fields and allow others to be changed.
need to add a proper message to the response explaining why some fields could not be changed.
Related issues
Updated by Go MAEDA about 4 years ago
- Related to Defect #8626: Setting status via API fails silently added
Updated by Vladimir Bocharov over 1 year ago
Good afternoon.
Will this problem be solved, as it would simplify the use of the API?
Updated by Vladimir Bocharov over 1 year ago
Go MAEDA, Good afternoon.
Will this defect be fixed in the next versions?
Actions