Atlassian Epic and Parent Fields Jira REST API Deprecation

We recommend using HAPI to access issues and their fields. HAPI gives you full access to all fields of the Parent issue, simplifies your code, improves readability, and helps safeguard it against future Atlassian deprecations.

You'll see these fields when working with Jira issues. See the before and after deprecation examples below:

• (Before) Non-HAPI
• (After) HAPI

def issueKey = 'TEST-1'
def issue = get("/rest/api/2/issue/${issueKey}")
  .header('Content-Type', 'application/json')
  .asObject(Map)
  
//get Epic Link
def epic = issue.fields.customfield_10014
epic

def issueKey = 'TEST-1'
def issue = Issues.getByKey(issueKey)
issue.getParentObject().getKey()

Similarly, with the Parent link, you can use HAPI to replace its usages and get access to the issue fields of the parent object.

Atlassian has published a detailed guide that provides examples, various API responses, and information on how they're changing. For cases where rewriting the code to use HAPI isn't straightforward, please refer to the guidance in Atlassian's documentation.