issue with the grouping of 'Child of' related tickets to their respective Parent

[Selcuk Tayar]

We are experiencing an issue with the grouping of 'Child of' related tickets to their respective Parent ticket in the Plans overview. Our hierarchy level is structured as follows.

At the top is the Portfolio level Secondly, there is the Program level Thirdly, there is the Team level.

We have the following initial situation. We have tickets of the Portfolio level and the Program level in the view, which are however separated from each other at the top and bottom even though they have a Parent-Child link.

If you drag and drop the individual Child tickets to the respective Parent, the Child ticket is directly grouped under the Parent and we have a desired grouping.

If you save the view, the tickets fly out of the grouping again.

Are we dealing with a bug here?

Thank you in advance.

[Selcuk Tayar]

Hello, we found the solution:

the problem lies in the fact that the overview in Plans only allows one parent link. Here, the field Parent Link is decisive. This field is a Jira Plans field and is set as soon as you manually incorporate a ticket into a parent. In this case, it is such that the requirement tickets already have an Epic Link, which also takes on the role of a parent ticket. So if you already have requirement tickets that have an Epic Link, you can indeed subsume these under a portfolio as a parent in the Plans overview, because it makes hierarchical sense, however, this requirement ticket will then have two parents, once its Epic and then the portfolio.

Solution: Delete the Epic Link of your requirement ticket, then you can subsume the ticket under the portfolio ticket.