Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3853

JSON formattage to add customer request Type custom field when creating via JIRA REST API

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • API and Integrations
    • None
    • 0
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Hi everybody,

      When I use JIRA REST APi to create an simple issue, everything works fine.

      I'm facing a problem when I add to my json request a custom field (Customer request type) "customfield_10025" :

      • I got a 400 error : "value of operation has to be a chain" ....

      Here is my json request :

      {
      "update": {},
      "fields": {
      "project":

      { "id": "10400" }

      ,
      "summary": "bla bla",
      "issuetype":

      { "id": "10201" }

      ,
      "priority":

      { "id": "3" }

      ,
      "description": "bla bla",

      "customfield_10202":

      { "id": "10100" }

      ,
      "customfield_10203": {
      "id": "10102",
      "child":

      { "id": "10103" }

      },
      "customfield_10025": {
      "requestType":

      { "id": "57" }

      }
      }
      }

      Can you help me to get the good syntax ?

      Many thanks

        1. Selection_026.png
          Selection_026.png
          21 kB
        2. Selection_025.png
          Selection_025.png
          44 kB
        3. Selection_024.png
          Selection_024.png
          15 kB

              Unassigned Unassigned
              8c14bbdc483c Adrien ESPIGUE
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: