Defect #17760

REST API to update custom fields in issues does not work

Added by Marco Descher about 7 years ago. Updated about 7 years ago.

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


Category:REST API
Target version:-
Resolution:Invalid Affected version:2.4.3


I just tried the following input, which returns

Started PUT "/issues/3273.xml?key=asdf" for 23233 at 2014-08-28 10:23:28 +0200
Processing by IssuesController#update as XML
  Parameters: {"issue"=>{"id"=>"3273", "subject"=>"", 
"description"=>nil, "start_date"=>"2014-08-20T00:00:00+02:00", "project_id"=>"0", "tracker_id"=>"0", 
"custom_fields"=>[{"id"=>"2", "name"=>"Abostatus", "value"=>"EXPIRED"}], "project"=>{"id"=>"3", 
"name"=>"Praxis Dr. Mustermann"}, "tracker"=>{"id"=>"4", "name"=>"Service"}}, "key"=>"asdf", "id"=>"3273"}
  Current user: mustermann (id=5)
Completed 200 OK in 27.9ms (Views: 0.4ms | ActiveRecord: 3.2ms

yet the value of the custom field in the issue is not changed, here the input

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <custom_fields type="array">
   <custom_field id="2" name="Abostatus">
 <project id="3" name="Praxis Dr. Mustermann"/>
 <tracker id="4" name="Service"/>

The respective field is defined as list with possible values.


#2 Updated by Marco Descher about 7 years ago

Here is the definition of the custom_field

<possible_values type="array">
<trackers><tracker id="4" name="Service"/></trackers>

#3 Updated by Marco Descher about 7 years ago

  • Status changed from New to Resolved

The issue was related with the access rights! I find it confusing, however, that redmine answered with a simple OK instead of a security related answer.

#4 Updated by Toshi MARUYAMA about 7 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid

Also available in: Atom PDF