Issue retrieval via REST should be consistent with retrieval via XML

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Won't Do
    • Component/s: Ecosystem
    • Environment:
      jira.atlassian.com

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Different results are obtained when retrieving an issue via the REST api compared to XML. Attached are the results obtained from the following two URLs:

      Observations:

      • xml contains resolution, omitted from json (looking at other issues, I see that resolution is included in the json if the issue is actually resolved. For unresolved issues, however, the value appears to be omitted)
      • xml contains field values for Participants (customfield_10150), json contains no values for this field
      • json contains values for "Support Request Message (IssueType:Bug)" (customfield_10250). This field is shown in the xml with no corresponding ID and no value.
      • json contains a field value for "Test Issue Creation Warning" (customfield_10301). This field is shown in the xml with no value.
      • json shows many more custom fields that aren't in XML (none appear to have a value associated with them, so perhaps that's why they're omitted?)
      • json shows information about watchers; xml does not
      • json shows fixVersion; xml does not unless there's a value

        1. JRA-23969.xml
          16 kB
        2. JRA-23969.json
          18 kB

            Assignee:
            Unassigned
            Reporter:
            DaveT
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: