nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filtering of Planning-tasks

AMIT GULATI

Hi,

I am trying to use the new planning-task functionality in Structure Plug-in. However, I am stuck with following problem

We have a hierarchy

Team 1 (grouped by label)

Program Increment

Epic 1

Epic 2

Planning Task 1

Planning Task 2

Team 2 (grouped by label)

Program Increment

Epic 3

Epic 4

Planning Task 1

Planning Task 2

All items under Program Increment are identified by a label provided in JIRA. Same label is provided to Planning tasks in Structure.

All looks good before I create a filter (on label) to see only a specific team's data. Even though label exists on Planning tasks, these get filtered out.

What is the right way to apply filter so that planning-tasks are also retained?

Accepted answers

Stepan Kholodov

Hello @AMIT GULATI

Since planning tasks are not issues, they can't be referenced in/recognized by JQL queries. When adding a filter to your structure, you can either remove all the planning tasks or keep all of them by selecting the 'Keep non-issues' option in the filter's configuration.

If you want to filter out some of the planning tasks along with the issues, you should use the Attribute Filter instead with a formula like this: search("label name",labels)

I hope this helps. If you have other questions about Structure, please reach out to us directly at our support portal.

Best regards,
Stepan
Tempo (the Structure app vendor)

All comments

Stepan Kholodov

Pasam Venkateshwarrao

@AMIT GULATI

Use "Filter by Attribute... (with Sub-Items)"

Instead of a plain filter:

Click the filter icon (funnel) in the Structure toolbar.
Select “Add Filter → Attribute...”
Choose: Label → contains → Team 1 (or your desired label)
Important: Enable "Keep sub-items of matching items"

This tells Structure:"Even if a sub-item (like a Planning Task) doesn't match the filter directly, keep it if it's a child of a matching item."

If your Planning Tasks are grouped by label as well, this can also help reinforce visibility.

Hope this helps

AMIT GULATI

@Pasam Venkateshwarrao Thanks Pasam. It worked. However, this will require me to create 15 filters since there are 15 different teams. Is there a better alternative?

Pasam Venkateshwarrao

@AMIT GULATI

Instead of 15 filters, use one base filter (e.g., all issues with team labels) and define quick filters inside Structure views.

How:

In Structure, go to Views → Manage Views
Define a view with multiple Quick Filters like:

labels = team1

labels = team2

labels in ("team1", "team2") // multi-team view

Hope this helps

AMIT GULATI

@Stepan When I filter and select Keep non-issues, it also shows the other teams which have Planning tasks, even though I just want to see a specific team's data.

Pasam Venkateshwarrao

@AMIT GULATI if it works for you can hit accept answer so that it will help to others those who are facing the same issue

Stepan Kholodov

@AMIT GULATI I only described to you what the JQL filter can do with planning tasks - it can either delete all of them, or it can keep all of them. To filter them out in a custom way, you need to use the Attribute Filter. If you have multiple teams, you can define the filter's formula to work with each team like this:

if search("team name 1",labels) or
search("team name 2",labels) or
search("team name 3", labels): 1

You can add as many team names to the formula as needed in the same fashion.

Best regards,
Stepan

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

addon-com.almworks.jira.structure

jira-data-center

data-center