Jira Filter Issue: Sub-Tasks Assigned to "Team X" Appearing Under "Team Y"

[Niklas Lachmann]

Dear community,

We are experiencing an issue with filtering in a Team-Managed project list view in Jira. Our issue hierarchy is structured as follows:

• EPIC → TASK → SUB-TASK
• Different teams are assigned to issues via the Team field.

Expected Behavior:

When filtering for a specific Team (e.g., "Team X"), we expect to see only the Epics, Tasks, and Sub-Tasks assigned to that team. Similarly, when filtering for the "Team Y", only "Team Y" issues should appear.

Actual Behavior:

• When filtering for "Team Y", sub-tasks from "Team X" (and even from other teams) are unexpectedly shown.
• The sub-tasks correctly inherit "Team X" from their parent tasks.
• However, these sub-tasks also have "Team Y" as a label as they are related, which might be interfering with the filtering logic.

Open Questions:

1. Is this a known Jira UI bug where the "Label" field interferes with the "Team" filter?
2. Could this be caused by an internal Jira filtering behavior specific to Team-Managed projects?
3. Are there any recommended best practices to avoid this issue when filtering by Team?

[Jehan Bhathena]

Hi @Niklas Lachmann ,

Please can you add 2 points of information, what JQL are you using to filter? And what field are your using to refering to in the JQL is it Label or Team?

For your Open questions:

1. Is this a known Jira UI bug where the "Label" field interferes with the "Team" filter?
   • You can check for any open issues here https://jira.atlassian.com/browse/JWMCLOUD-859?jql=project%20in%20(CLOUD%2C%20CONFCLOUD%2C%20JSWCLOUD%2C%20JRACLOUD%2C%20JSDCLOUD%2C%20JWMCLOUD)
     
2. Could this be caused by an internal Jira filtering behavior specific to Team-Managed projects? :
   • Will be able to tell this after I see the JQL
3. Are there any recommended best practices to avoid this issue when filtering by Team?
   • If a Parent is assigned Team A, then all the child tickets also get the Team A value (from what I'm aware of). 

[Niklas Lachmann]

Hi @Jehan Bhathena ,

Thanks for your response. We’ve found that the issue likely stems from sub-tasks inheriting team assignments from their parent tasks in our Team-Managed project.

We learned that sub-tasks are tied to their parents and don’t function independently, so even though parent tasks changed from “Team X” to “Team Y,” the filter still picks up sub-tasks under “Team X” due to their history. We figured the Team field on sub-tasks may be irrelevant.

Could you confirm our assumption?

Best,
Niklas

[Jehan Bhathena]

That is correct, a Sub-Task inherits most of it's values from the parent, since it's not an individual task on it's own.

If you want to add a different team to 2 tickets, then you'd have to do that via TASKS or any issue type above Sub-Tasks.

[Niklas Lachmann]

We actually changed the teams on these 2 tickets (parent tasks). But it is not possible to change the team for the sub-tasks after the creation. They will always be picked up by the Team they were „born“ with. Right?

[Jehan Bhathena]

"They will always be picked up by the Team they were „born“ with" : They will take the values of the "Parent". If the Parent's TEAM is updated after the sub-task is created, the associated sub-task's TEAM value will change too.

[Niklas Lachmann]

And there is the issue. The parents team was updated. So was their child sub-tasks automatically. But when filtering for the „new“ team only the parent tasks are picked up. The child sub-tasks are still picked up by the „old“ team. Although having the correct „new“ team assigned.

[Jehan Bhathena]

Ahh ok,

then I would recommend reporting that to the Atlassian support team to verify the bug.

You can report this here https://support.atlassian.com/

[Hannes Obweger - JXL for Jira]

Hi @Niklas Lachmann

this indeed looks incorrect to me. Please keep us posted on what Support says!

Also, just to put it out there in case it is useful: If you're open to solutions from the Atlassian Marketplace, this would work as expected in the app that my team and I are working on: JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a range of advanced features - including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting - and works across any number of projects.

Plus, team filtering works as expected for all issue types, including sub-tasks.

This is how it looks in action:

Any questions just let me know,

Best,

Hannes