Update 18th January 2024:
Hi all,
An update to this rollout. (Click here to learn more about the different release tracks)
---
[The below article is for Jira Software cloud only]
👋 Hi Jira Community!
Over the past year, we’ve been providing updates around renaming epics in your company-managed projects.
When we first announced this work, we let you know that we were improving the way you associate epics with your bugs, stories and tasks in Jira by:
replacing the existing Epic link and Parent link fields with the Parent field in the issue view
adding the Add parent feature seen in team-managed projects to the company-managed issue view
replacing the Epic link and Parent link fields with the Parent field when creating new issues
replacing the Epic link and Parent link fields with the Parent field when creating new workflow transitions
extending the parent
JQL function to incorporate the functionality of the epic link
, parent link
and parentEpic
functions.
In this post, we’ll outline what these updates include and any steps you should take to prepare for these changes.
The Epic link and Parent link fields on the issue view will soon be replaced by a single Parent field.
We also heard from you that adding epics to issues can sometimes be difficult, so we’re adding the ability to add a parent directly from your issue’s breadcrumb, consistent with how you work in team-managed projects.
You’ll also be able to add a parent from the Actions (...) menu or using keyboard shortcuts.
In Jira Software Premium, the Parent link will also move to the breadcrumb – you’ll no longer need to configure the issue view for this to appear.
You won’t need to do anything in Jira to prepare for this particular update.
If your issue view includes the Epic link or Parent link fields, we will automatically replace these fields and migrate any existing values to the new Parent field.
When creating new issues in Jira, the Epic link and Parent link fields will be replaced by a single Parent field.
You won’t need to do anything in Jira to prepare for this particular update.
If your issue create layout includes the Epic link or Parent link fields, we will automatically replace these fields with the new Parent field.
When creating new workflow transitions in Jira, the Epic link and Parent link fields will be replaced by the Parent field in the workflow editor.
You won’t need to do anything to prepare for this particular update.
Any existing use of Epic link and Parent link in your workflow transitions will continue to work after this update, however new workflow transitions will not be able to use the Epic link and Parent link fields and should use the Parent field instead.
To reflect these updates, we’re also making some small changes to our JQL functions. The parent
JQL function will extend to incorporate the functionality of the epic link
, parent link
and parentEpic
functions.
While these functions will continue to work in your existing JQL searches, you’ll no longer be able to use them in new searches. Instead, teams should begin using the parent
JQL function.
The majority of saved searches and JQL queries (including JQL-backed boards) will continue to show the same results when this update rolls out – you won’t need to do anything to prepare.
In some cases, however, the results of JQL queries that include the parent
JQL function may show more results than they previously did. This may impact your existing saved filters if you’re using:
parent is empty
parent is not empty
parent = xyz
parent != xyz
parent in (xyz, abc)
parent not in (xyz, abc)
NOTE: This update will only affect issues in company-managed projects. Issues in team-managed projects will not be affected.
For more information on how this might impact you and our recommended solutions, view our documentation.
We'll begin progressively rolling out these changes later this year. We will keep you updated closer to the release.
If you have any questions or feedback on these updates, let us know in the comments below. Thanks!
Irene
Principal Product Manager
Atlassian
Sydney, Australia
7 accepted answers
185 comments