Defect #7158

Issues Custom fields not in json

Added by Dimitri Sapunou over 11 years ago. Updated over 11 years ago.

Status:ClosedStart date:2010-12-22
Priority:NormalDue date:
Assignee:-% Done:


Category:REST APIEstimated time:0.50 hour
Target version:-
Resolution:Duplicate Affected version:


In XML everything ok.

<issues type="array">
        <project name="c4" id="1"/>
        <tracker name="Unterst├╝tzung" id="3"/>
        <status name="Neu" id="1"/>
        <priority name="Dringend" id="6"/>
        <author name="User Name Admin" id="1"/>
        <assigned_to name="User Name Admin" id="1"/>
        <subject>test uuid</subject>
            <custom_field name="issues_uuid" id="3">f0df939d-65a7-bf84-71e9-fdb54373ecfc</custom_field>
        <created_on>Wed Dec 22 09:39:04 +0100 2010</created_on>
        <updated_on>Wed Dec 22 09:49:54 +0100 2010</updated_on>

In JSON missing custom field: issues_uuid.

"created_on":"2010/12/22 09:39:04 +0100",
"updated_on":"2010/12/22 09:49:54 +0100",
"subject":"test uuid",

Related issues

Duplicates Redmine - Defect #6136: JSON API holds less information than XML API Closed 2010-08-13


#1 Updated by Jean-Philippe Lang over 11 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Same as #6136.

Also available in: Atom PDF