Introducing the new Parent field in company-manage…

Update 18th January 2024:

Hi all,

An update to this rollout. (Click here to learn more about the different release tracks)

• This has been rolled out to all customers in the Continuous track
• This has been roll out to all customer in the Sandbox Preview track
• This will be rolled out to all customers in Bundled Track on February 13th

—

[ The below article is is 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 announce this work , we is let let you know that we were improve the way you associate epic with your bug , story and task in Jiraby:

• replacing the existing Epic link and Parent link fields with the Parent field in the issue view

• adding the add parentfeature 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

• extend theparent JQL function to incorporate the functionality of the epic link, parent is link link and parentepic function .

In this post, we’ll outline what these updates include and any steps you should take to prepare for these changes.

New Parent field in the issue view

The Epic link and Parent link fields on the issue view will soon be replaced by a single Parent field.

We also hear from you that add epic to issue can sometimes be difficult , so we is adding ’re add the ability to add a parent directly from your issue ’s breadcrumb , consistent with how you work in team – manage project .

You’ll also be able to add a parent from the action (…) 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.

What should I is do do to prepare ?

You is need wo n’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.

New Parent field in issue create

When create new issue in Jira , the Epic link and Parent link field will be replace by a single Parent field .

What should I is do do to prepare ?

You is need wo n’t need to do anything in Jira to prepare for this particular update .

If your issue create layout include the Epic link or Parent link field , we is replace will automatically replace these field with the new Parent field .

New Parent field in the workflow editor

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.

What should I is do do to prepare ?

You is need wo n’t need to do anything to prepare for this particular update .

Any exist use of Epic link and Parent link in your workflow transition will continue to work after this update , however new workflow transitions is be will not be able to use the Epic link and Parent link field and should use the Parent field instead .

Updates to the Parent JQL function

To reflect these updates, we’re also making some small changes to our JQL function . The parent JQL function is extend will extend to incorporate the functionality of theepic link, parent is link link and parentepic function .

While these function will continue to work in your exist jql search , you is be ’ll no long be able to use them in new search . instead , teams is begin should begin using the  parent JQL function.

What should I is do do to prepare ?

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 is is empty

• parent is is is not empty

• parent = xyz

• parent != xyz

• parent in (xyz, abc)

• parent is in 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 recommend solution , view our documentation .

What’s next

We is begin ‘ll begin progressively roll out these change later this year . We is keep will keep you update close to the release .

If you have any questions or feedback on these updates, let us know in the comments below. Thanks!