Project

General

Profile

Actions

Defect #10233

open

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

Added by Alex Last about 12 years ago. Updated 8 months ago.

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

Related to Redmine - Defect #8626: Setting status via API fails silentlyConfirmed2011-06-16

Actions
Actions #1

Updated by Go MAEDA about 3 years ago

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

Updated by Go MAEDA about 3 years ago

  • Status changed from New to Confirmed
Actions #3

Updated by Vladimir Bocharov 10 months ago

Good afternoon.
Will this problem be solved, as it would simplify the use of the API?

Actions #4

Updated by Vladimir Bocharov 8 months ago

Go MAEDA, Good afternoon.
Will this defect be fixed in the next versions?

Actions

Also available in: Atom PDF