Defect #10233

"update issue" silently ignores "status" field if the user is not part of the project, but changes other fields

Added by Alex Last almost 10 years ago. Updated 12 months ago.

Status:ConfirmedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:REST API
Target version:-
Resolution: Affected version:1.3.1

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

Related to Redmine - Defect #8626: Setting status via API fails silently Confirmed 2011-06-16

History

#1 Updated by Go MAEDA 12 months ago

  • Related to Defect #8626: Setting status via API fails silently added

#2 Updated by Go MAEDA 12 months ago

  • Status changed from New to Confirmed

Also available in: Atom PDF