Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
The following changes have not been rolled out yet. We’ll update here when we have more specific timelines to share.
Currently, the epic-link connects issues from the base level (containing stories, bugs, tasks) to epics, and the parent-link connects epics to issues at higher levels for those who have Jira Software Cloud Premium.
In 2022 and 2023, we'll be moving towards a single way of representing parent/child relationships to give you a simple, consistent experience for all levels in your Jira Software projects. epic-link and parent-link in company-managed projects will be replaced with the parent concept already used in team-managed projects.
Note: The following updates will apply automatically to your Jira Software instance, there will be no action required from you. The following changes apply to company-managed projects only.
Updates to the issue view
The parent of an issue will move from appearing in the epic-link or parent-link field in the right panel, to the breadcrumb at the top, consistent with team-managed projects. Any existing epic-links will automatically move to the breadcrumb – no user action will be required.
For Jira Software Cloud Premium users, the parent-link will also move to the breadcrumb, and will no longer need issue configuration to appear.
The old parenting experience using the Epic Link field
The old parenting experience using Parent Link field
The new breadcrumb parenting experience
Change parent in the more (…) menu on the issue view
Change an issue’s parent via the more (…) menu, or by clicking View all in the breadcrumb
Updates to boards/backlogs
The board and backlog experience will not change – you will continue to see parent epics appear in the lozenge on each listed issue.
Updates to issue create
The epic-link field and parent-link fields will be replaced by a single parent field in the issue create experience. Consistent with current functionality, you will be able to exclude 'done' issues when searching for a parent, and the issue search results will only show issues from 1 level above.
Updates to JQL, issue searches and saved searches
Now: All existing epic-link data has been copied to the new parent field – any new epic-links you create will also automatically copy across to the parent field. Users will not be able to create new JQL or issue searches using epic-link, they will be directed to use parent instead. All saved searches/JQL queries including JQL-backed boards will continue to show the same results*, adding new or editing existing epic links will result in updated results for saved searches and queries.
Essentially, anything you’ve saved will continue to work as expected, but we’ll guide you to using parent instead of epic-link for creating anything new.
In late 2022 the above changes will apply to the parent-link field as well.
In 2023 we will convert all existing saved JQL and issue searches containing epic-link and parent-link to parent. Search results will not be affected* and no user action will be required. More specific dates will be added here as we get closer to the update.
*Note that there are edge cases in which you will get more results than you did previously because both epic-link and parent-link values have been copied to parent, and now epic-link JQL is reading parent values. Different results will arise if you are using != or not in or is not empty in your JQL. For example if you had the below issues, Epic Link != Epic 1 previously returned no results, now it is effectively querying parent != Epic 1 and returns Issue 3.
Impact to marketplace APIs
Marketplace vendors have been notified of these changes with 6+ months notice – see: Deprecation of the Epic Link, Parent Link and other related fields in REST APIs and webhooks
What do you have to do? Will existing epic-links be preserved?
These updates will apply automatically to your Jira Software instance, there will be no actions required from you. All your existing epic-links and parent-links will be copied to parent, any updates to epic-link and parent-link will automatically update the parent value.
Are epic colors affected? You’ll still see epics with colored lozenges in boards and backlogs, there are minor changes upcoming to epic colors – learn more about these changes: Upcoming changes to epic fields in company-managed projects
Will I still be able to see the epic-link data after these changes are made? Yes, you'll still be able to access these fields JQL and issue search.
What happens to the parent value if I update the epic-link? The parent value will automatically be updated.
Need more help?
If you have any questions, add a comment here or please contact our support team.
Was this helpful?