プロジェクト

全般

プロフィール

Vote #77833

完了

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

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
REST API_32
対象バージョン:
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
32
version_id:
119
issue_org_id:
23921
author_id:
93741
assigned_to_id:
1
comments:
4
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
110
ステータス-->[Closed]

説明

Hi,

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.


journals

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Fixed by r16055.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


related_issues

relates,Closed,26063,Users can assign a user/group which is not a member of current project, or even a user that doesn't exist

Admin Redmine さんが約4年前に更新

  • カテゴリREST API_32 にセット
  • 対象バージョン3.4.0_119 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0