Team field Inheritance from Parent to Child

[John Izquierdo]

Hi, all!

I've noticed in work management space (and probably JSM and Software too) that when I:

1. Create a Task (parent ticket) and assign the Team field
2. Then, create a subtask (child) it inherits the value of the Team field from the parent

I've checked to make sure there are no global automations setup. That there's not a settings in the Work Type or in the Space settings itself.

Is there a way to disable child inheritance from the parent or will an automation be needed to accomplish this?

Thanks in advance to anyone who can help!

[Trudy Claspill]

Hello @John Izquierdo 

This question came up in 2025. It doesn't appear that disabling this is possible.

https://community.atlassian.com/forums/Jira-questions/How-to-disable-Team-field-inheritance-in-sub-tasks/qaq-p/3070605

Based on my experimentation it is not possible through the UI to directly modify the Team field in a subtask. Such work item types appear to only be able to get a value in the Team field by inheriting it.

[Alexander Stern _ Shern Consulting OÜ]

Hi John Izquierdo,

What you are seeing is usually default Jira behavior rather than an automation. Some fields, especially planning or ownership fields like Team, can be copied from the parent issue when a subtask is created.

As far as I know, there is no native setting to disable only Team field inheritance at project level.

The most common solution would be to use an automation rule such as:

Trigger: Issue created
Condition: Issue type = Subtask
Action: Clear Team field or set another value

That gives you control without affecting the parent task.

It may also behave differently depending on whether this is team-managed or company-managed Jira, and whether you are using the official Atlassian Team field or a custom field.

If no one finds a hidden setting, automation is likely the most practical route here.