Scenario:

In Jira plans, we have an ability to use the Group By: feature to group items using parameters such as for e.g. a custom field., whenever this filter is applied, we see 2 category of sections 1) having custom field values 2) Unassigned section. 

The challenge is there are some issues which appears in both sections leading to end user confusions as shown below. 

This behaviour is happening due to Group By: works based on hierarchy so it will show the entire hierarchy, because some of the child issues might not have the assigned values of the Custom field so the plans can't display the incomplete hierarchy. This is explained in this documentation. 

Issues appearing in the Unassigned swimlane when Grouping by...

Workaround:

As a workaround, use a Filter with a specific hierarchy only for a specific view, for example, 1 Filter view for the Portfolio feature while the other Filter view for the Full Hierarchy, as demonstrated over the call.

• Filter work items on your plan (based on Hierarchy)

• Save a new view in your plan