Team field is empty and cannot be filled when creating a subtask, but Team is mandatory

[Yaroslav Nelin]

We are running a company-managed software project (Jira Premium, with Advanced Roadmaps / Plans enabled).

Problem:
When we create a subtask from a parent work item, the Team field appears in the "Add subtask" form as required (marked with *) but is empty and cannot be edited/selected — the field is greyed out with a message indicating that the team cannot be changed for subtasks. When we click Create, we get the validation error:

Field "Team" is required.

This makes it impossible to create subtasks at all through the inline "Add subtask" action.

What we expected:
Based on Atlassian documentation, the subtask should inherit the Team value from its parent work item automatically. For existing subtasks, this does appear to work — for example, subtask CO-7047 has Team = "Telematics", inherited from its parent CO-5316 (also "Telematics"). However, for newly created subtasks, the Team field is empty at creation time and the required validation blocks creation.

What we have already checked/tried on our side:

1. The Field Configuration does NOT list Team as required (only Issue Type, Reporter, and Summary are required there). The mandatory behavior on Team is enforced by Jira itself.
2. There are no workflow validators and no automation rules that make Team required.
3. We created a dedicated subtask screen without the Team field and mapped it to the Sub-task issue type. The form then opened without the Team field, but clicking Create still returned "Field Team is required." So removing Team from the screen does not bypass the backend validation. (We have since reverted this change.)
4. We tried building an automation rule ("copy Team from parent to subtask"), but automation runs after the work item is created, while the "Team is required" validation blocks before creation — so it does not help for manual subtask creation.
5. In global Fields, the Team field is shown as Locked with the note: "This field was created by Jira or a plugin, and can't be edited." There is no option to set a default value, configure inheritance, or change its required behavior.
6. The global Create button does not offer "Sub-task" as an issue type, and its Parent field only accepts Epics — so subtasks can only be created via the inline "Add subtask" action, which is exactly where the Team validation blocks us.

Our questions/request:

• Why is the Team value not inherited/pre-filled in the "Add subtask" form at creation time, even though it works for existing subtasks and inheritance is expected?
• How can we make the parent's Team automatically populate the subtask's Team field at the moment the creation window opens, so that Team is not empty and the required validation passes?
• If this is a known limitation or bug, is there a supported workaround or configuration for a company-managed Premium project with Plans enabled?

[James Gamble]

Hola Yaroslav,

What you’re describing looks like a Jira Cloud defect rather than a configuration problem. Atlassian’s own documentation says that a subtask inherits its Team assignment from its parent and that the Team field can’t be updated independently on the subtask.

There’s also a Jira Cloud bug that closely matches this behavior. JRACLOUD-89943 documents inline subtask creation failing because Jira tries to validate the inherited Team field during creation, even though the user isn’t supposed to set that field manually. Atlassian recorded no known workaround before the issue was eventually closed as timed out.

Your troubleshooting also rules out most of the usual configuration causes. You’ve confirmed that Team isn’t required in the field configuration; no validators or automation rules are enforcing it; removing Team from the subtask screen doesn’t help; and automation can’t populate it because creation is blocked before the rule can run.

I wouldn’t try to unlock or otherwise modify the system Team field. Its inheritance behavior is intentional, and Atlassian specifically documents that attempts to update Team directly on a subtask fail because the value comes from the parent.

Since you’re on Premium, I’d open an Atlassian Support case and reference JRACLOUD-89943. Include one affected parent/subtask example, the exact creation path, screenshots showing the disabled Team field and validation error, and confirmation that the parent already has a Team assigned. I’d also mention that existing subtasks inherit Team correctly, while only new inline creation is blocked, because that helps distinguish the inheritance mechanism from the creation defect.

I don’t see a supported configuration that’ll pre-populate the Team field manually when the dialog opens. Jira is supposed to handle that inheritance itself, so fixing the underlying creation behavior is really the appropriate path here.

Thanks,

James