Defect #23921

REST API Issue PUT responds 200 OK even when it can't set assigned_to_id

Added by Fran Fabrizio almost 2 years ago. Updated over 1 year ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:


Category:REST API
Target version:3.4.0
Resolution:Fixed Affected version:3.3.0



I ran across an issue with the REST API that responded with a 200 OK when I think it should respond with an error.

If I try to PUT this to an existing issue:

{ "issue": {
 "assigned_to_id": "19" 

it will respond 200 OK even if it can't change the assigned_to_id to 19, for instance if user ID 19 does not have an assignable role on the project. Because the API reported a 200 OK, this led to a lot of confused debugging. A 422 return with appropriate error message in the body might be more useful.

Related issues

Related to Redmine - Defect #26063: Users can assign a user/group which is not a member of cu... Closed

Associated revisions

Revision 16055
Added by Jean-Philippe Lang over 1 year ago

Enforce issue assignee validation (#23921).


#1 Updated by Toshi MARUYAMA almost 2 years ago

  • Description updated (diff)

#2 Updated by Toshi MARUYAMA over 1 year ago

  • Target version set to 3.4.0

#3 Updated by Jean-Philippe Lang over 1 year ago

  • Status changed from New to Closed
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

Fixed by r16055.

#4 Updated by Go MAEDA about 1 year ago

  • Related to Defect #26063: Users can assign a user/group which is not a member of current project, or even a user that doesn't exist added

Also available in: Atom PDF