Why is "Team" field locked and required for subtasks while I cannot edit it when creating a subtask?

[Vesa Recica]

So, the "team" field shows as locked in the configuration for my project so I cannot remove it from the required fields. In the meantime, I have stories for which my team is trying to add subtasks to and they are unable to do that because it shows "team" field is required even though it is not editable at a sub-task level.

I tried adding the team to that story so that the subtask could inherit it but it is not working.

[Walter Buggenhout]

Hi @Vesa Recica and welcome to the Community!

Have a look at the workflow associated with subtasks in your project and verify if there isn't a validator on the create transition that requires the team field.

As far as I can tell, I am quite sure that Team is not a required field by default in Jira and since you can't edit its behaviour through a field configuration, there must another driver for this behaviour.

Hope this helps!

[Vesa Recica]

Hi Walter, thank you for your answer! I have actually tried checking into the validators and the workflow does not have any so I'm not sure where the problem could be coming from...

[Walter Buggenhout]

Very hard to judge from a distance ... something else I've seen happening is that there is another Team field in Jira that is causing the problem. The tool does not prevent having multiple fields with the same name; have you checked that as an option?