What is changing?
We’re deprecating the Epic Link and Parent values returned in field in issue history changelogs for company-managed projects (previously known as classic projects). These values will be replaced with IssueParentAssociation , a value used in team-managed projects (previously known as next gen projects). IssueParentAssociation will be the new source of truth in the issue history changelogs for information about issue reparenting, that is, changing epic links and subtask parents.
This change impacts all issue operations and webhooks that return changelogs. For an exhaustive list of the deprecations and what it impacts, see the official deprecation notice Deprecation notice: Issue changelogs for issue parenting.
During the deprecation period, the Epic Link and Parent values will be returned alongside IssueParentAssociation in order to facilitate migration.
Examples
For changelog items for updates to the Epic Link field of issues, instead of returning:
"items": [
...,
{
"field": "Epic Link",
"fieldtype": "custom",
"fieldId": "customfield_id",
"from": "1234",
"fromString": "ABC-1",
"to": "4567",
"toString": "ABC-2"
},
...
]
we will return:
"items": [
...,
{
"field": "IssueParentAssociation",
"fieldtype": "jira",
"from": "1234",
"fromString": "ABC-1",
"to": "4567",
"toString": "ABC-2"
},
...
]
For changelog items for subtask re-parenting, instead of returning:
"items": [
...,
{
"field": "Parent",
"fieldtype": "jira",
"from": null,
"fromString": null,
"to": "1234",
"toString": "ABC-1"
},
...
]
we will return:
"items": [
...,
{
"field": "IssueParentAssociation",
"fieldtype": "jira",
"from": null,
"fromString": null,
"to": "1234",
"toString": "ABC-1"
},
...
]
Why is Atlassian making this change?
Atlassian is standardizing reparenting of issues across the Jira products. This means we are changing our underlying data model so that all issue parenting goes through one common code path. As a result we are also consolidating the values Epic Link and Parent that appear in issue history changelogs. This is just one of the many changes we have been making around issue type hierarchy, with more to come. For prior deprecations relating to this, see:
- Deprecation notice: Hierarchy level changes
- Change notice: Removing hierarchy level IDs from next-gen APIs
What do I need to do?
If your app is dependent on the Parent and Epic Link values in the changelogs of issues, please migrate and consume IssueParentAssociation instead.
We will facilitate this migration by returning changelog items for both the old and new values for each reparenting update during the deprecation period.
By when do I need to do it?
First, we will return IssueParentAssociation in addition to existing changelog items for each reparenting update starting on or before 10 June 2021 . We will ceased to return issue history changelog items containing the Epic Link and Parent values on 10 December 2021 .