Project

General

Profile

Actions

Defect #6128

closed

"assigned_to" seem to be ignored when creating issues via REST API

Added by Alex Last about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
REST API
Target version:
-
Start date:
2010-08-13
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

sending request:

POST http://172.17.10.53:3000/issues.xml HTTP/1.1  -> <issue><project_id>ace</project_id><subject>test zzx</subject><assigned_to name="Alexey Skor" id="19640"/></issue>

response:

HTTP/1.1 201 Created

but the new issue's "assignee" is empty. I verified there's a user with such id.
I'm trying to use the same <issue> format as I see in the response from Redmine when I retrieve issues list.

is this REST API's limitation that assignee can't be set on issue creation or I should use different format for this field? if it's the latter, then I hope there's a documentation somewhere about that.

Actions

Also available in: Atom PDF