Parent Link custom field: Invalid values to be removed

👋 Hi friends!

Over the past year, we’ve been sharing updates on our plans to allow you to rename epics in your company-managed projects, including the introduction of the Parent field that will soon replace the existing Epic link and Parent link fields.

As part of these changes, we’ll be removing parent link values that become invalid as a result of changes to your issue type hierarchy.

What’s an invalid parent link value?

The value of the Parent link custom field can become invalid if:

  • The child issue is changed to an issue type on a different hierarchy level

  • The parent issue is changed to an issue type on a different hierarchy level

  • The child issue’s issue type is moved to a different hierarchy level

  • The parent issue’s issue type is moved to a different hierarchy level

For example, say you have an epic called EpicX (level 1) with a Parent link field set to an issue called InitiativeY (level 2). This is a valid parent link value as InitiativeY is on a hierarchy level above EpicX.

However, if the initiative issue type is moved to level 1, EpicX and InitiativeY will both be on the same hierarchy level, and the parent link value will be invalid.

Why are we making this change?

Previously, the Parent link field would not remove invalid parent-child relationships. These values would instead be hidden from users. This meant that if the relationship became valid later, it would become visible to users again.

So, in the example above, if the initiative issue type was moved back to level 2, the parent link value would become valid again and be displayed to users.

This behavior was often unintended by users – by removing these invalid parent link values, this will no longer occur. This is also more closely aligned to the behavior of the Parent field that will soon replace Parent link.


If you have any comments or questions, please let us know below.

7 comments

Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 23, 2023

Hi @Anne Jang Is this change effective for issue type hierarchy both above AND below Epic level?

  1. Parent link between Epic and the Initative level (above Epic level)
    Example: Initiative -> Epic (parent -> child)
  2. Parent link between Epic and the issues within the Epic (below Epic level)
    Example: Epic -> Task/Story/.... (parent -> child)
Like Dan Tombs likes this
Anne Jang
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 25, 2023

Hi @Dave Mathijs, yes the changes are effective for all levels.

Technically the parent link custom field doesn't allow you to select an Epic. So for the "below Epic level" example, a task/story/... etc can't have the parent link set to an Epic.

But the task/story/.. can have the parent link field value set to parent with a different issuetype on the Epic level and we would remove these values if they become invalid.

Like # people like this
Dan Tombs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 27, 2023

Really good to continue seeing this move forward. Think it is vital the clean-up happens to make sure experience is correct.

Like # people like this
Nikki Zavadska _Appfire_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 29, 2023

It's great to see progress against enabling us to rename Epics in the company-managed projects and bringing some of the functionality from team-managed to company-managed projects.

 

Just a side question related to the aligning of functionalities are there any plans of introducing images to be shown on the kanban cards in company-managed projects the same way they are on the team-managed projects or Trello?

Anne Jang
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 29, 2023

Hi @Nikki Zavadska _Appfire_ 

Great to hear it’s welcome news.

I’ve spoken to the team looking at changing the kanban cards in company-managed-projects. They said they have no concrete plans as yet to show images, but will be exploring it as an option in the future.

Elodie Dechaintre
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 7, 2023

Today, we can have an epic in one project and its children in another. Will the 'Parent' system still allow this?

Like Casey Gould likes this
Anne Jang
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 10, 2023

Hi @Elodie Dechaintre - the parent field will be consistent with existing rules for what is considered a valid parent.

For example, in company managed projects, you can have a epic in one project but children in another.
However in team managed projects, epics and their children must be in the same project.
Subtasks must have a parent in the same project for both company managed and team managed projects.

Like Elodie Dechaintre likes this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events