Atlassian is standardizing how issue type hierarchies are created and configured across Jira, Jira Software, Jira Service Management, and Advanced Roadmaps for company-managed and team-managed projects. From 1 November 2021, issue links will not be used to link subtasks to their parents and epics to stories. Instead those relationships can be determined using issue parent associations, a concept introduced for team-managed projects. As a result, Jira APIs will not return issue-parent relationships in issuelink-related operations.
There are several different hierarchy structures that have to be reconciled when developing tools for the Jira product range. Standardizing on one hierarchy format makes it easier to develop tools and integrate products. This simplification will help us create and roll out new features to customers faster.
Plan to migrate away from using issuelinks to fetch issue/parent relationships in your hierarchies.
For non-bulk tasks, swap the hierarchy out for the parentId field.
A new operation will be provided to fetch issue/parent relationship data for bulk tasks.
| Operation | Method | Endpoint | Scope | Deprecation |
|---|---|---|---|---|
| Get issues for backlog | GET | /rest/agile/1.0/board/{boardId}/backlog | Response | issueLinks of the parent/child type in response body |
| Get issues without epic for board | GET | /rest/agile/1.0/board/{boardId}/epic/none/issue | Response | issueLinks of the parent/child type in response body |
| Get board issues for epic | GET | /rest/agile/1.0/board/{boardId}/epic/{epicId}/issue | Response | issueLinks of the parent/child type in response body |
| Get issues for board | GET | /rest/agile/1.0/board/{boardId}/issue | Response | issueLinks of the parent/child type in response body |
| Get board issues for sprint | GET | /rest/agile/1.0/board/{boardId}/sprint/{sprintId}/issue | Response | issueLinks of the parent/child type in response body |
| Get issues without epic | GET | /rest/agile/1.0/epic/none/issue | Response | issueLinks of the parent/child type in response body |
| Get issues for epic | GET | /rest/agile/1.0/epic/{epicIdOrKey}/issue | Response | issueLinks of the parent/child type in response body |
| Get issue | GET | /rest/agile/1.0/issue/{issueIdOrKey} | Response | issueLinks of the parent/child type in response body |
| Get issues for sprint | GET | /rest/agile/1.0/sprint/{sprintId}/issue | Response | issueLinks of the parent/child type in response body |
| Operation | Method | Endpoint | Scope | Deprecation |
|---|---|---|---|---|
| Get issue | GET | /rest/api/3/issue/{issueIdOrKey} | Request Response | issueLinks of the parent/child type in request GET params, issueLinks of the parent/child type in response body |
| Create issue | POST | /rest/api/3/issue | Request | issueLinks of the parent/child type in request GET params |
| Bulk create issue | POST | /rest/api/3/issue/bulk | Request | issueLinks of the parent/child type in request GET params |
| Search for issues using JQL | GET | /rest/api/3/search | Request Response | issueLinks of the parent/child type in request GET params |
| Search for issues using JQL | POST | /rest/api/3/search | Request Response | issueLinks of the parent/child type in request GET params |
| Create issue type | POST | /rest/api/3/issuetype | Request | type attribute in request GET params |
| Get project | GET | /rest/api/3/project/{projectIdOrKey} | Request Response | The expand request parameter will no longer support issueTypeHierarchy and no corresponding data will be included in the response. |
| Update project | PUT | /rest/api/3/project/{projectIdOrKey} | Request Response | The expand request parameter will no longer support issueTypeHierarchy and no corresponding data will be included in the response. |
| Operation | Method | Endpoint | Scope | Deprecation |
|---|---|---|---|---|
| Get issue | GET | /rest/api/2/issue/{issueIdOrKey} | Request Response | issueLinks of the parent/child type in request GET params, issueLinks of the parent/child type in response body |
| Create issue | POST | /rest/api/2/issue | Request | issueLinks of the parent/child type in request GET params |
| Bulk create issue | POST | /rest/api/2/issue/bulk | Request | issueLinks of the parent/child type in request GET params |
| Search for issues using JQL | GET | /rest/api/2/search | Request Response | issueLinks of the parent/child type in request GET params |
| Search for issues using JQL | POST | /rest/api/2/search | Request Response | issueLinks of the parent/child type in request GET params |
| Create issue type | POST | /rest/api/2/issuetype | Request | type attribute in request GET params |
| Get project | GET | /rest/api/2/project/{projectIdOrKey} | Request Response | The expand request parameter will no longer support issueTypeHierarchy and no corresponding data will be included in the response. |
| Update project | PUT | /rest/api/2/project/{projectIdOrKey} | Request Response | The expand request parameter will no longer support issueTypeHierarchy and no corresponding data will be included in the response. |
Rate this page: