Deprecation of the Epic Link, Parent Link and other related fields in REST APIs and webhooks for updating Jira issues

Jira Development Jira Cloud
1

Will Epic Link or Parent Link be removed from the “/rest/api/3/field” endpoint?

No. The “Get fields” endpoint ( GET /rest/api/3/field ) will continue returning these fields.

Referring to the “Get Fields” endpoint above, may I know why is it not returning the new parent field and still returning epic link field as so:

{
      "id":"customfield_10014",
      "key":"customfield_10014",
      "name":"Epic Link",
      "untranslatedName":"Epic Link",
      "custom":true,
      "orderable":true,
      "navigable":true,
      "searchable":true,
      "clauseNames":[
         "cf[10014]",
         "Epic Link"
      ],
      "schema":{
         "type":"any",
         "custom":"com.pyxis.greenhopper.jira:gh-epic-link",
         "customId":10014
      }
   }

This is an issue for us because we are using this endpoint to get the fields and use it to update Jira Issues via PUT /rest/api/2/issue/{issueIdOrKey} which will only be able to consume the parent field after the deprecation.

4 Likes