Either adding 'team' to sub-task automatically or removing it altogether

[Christian Macedo]

I'd like to add a sub-task to a ticket on Jira cloud. I also have the 'Team' value enabled such that any ticket must have the team filled in. However this has also affected the subtasks. 

What can I do to either:

1. Have the team inherited from the parent and populated. or
2. Have the sub-tasks not require 'Team' at all. 

At the moment I get to the following point. Both requiring the Team field to be populated without the 'Team' field being editable. 

[Vivi Rishe]

Same. Can you not edit the team or sprint in sub-tasks?

[Trudy Claspill]

@Vivi Rishe 

You should not be trying to edit Sprint in sub-tasks.

The design of Jira is such that sub-tasks are considered part of the sprint to which their parent story is assigned. I would suggest for that aspect of your issue you consider opening a separate thread for discussion.

We don't use the Team field at my company, so I have not been able to add anything about that issue to this thread, unfortunately.

[Allan Macedo]

I also have this problem.

[Trudy Claspill]

Hello @Christian Macedo 

Welcome to the community.

Is this for a Classic project or a Next-Gen project?

If for a Classic project then you could implement solution #2 by creating a separate field configuration for your sub-task issues, and in that field configuration make the Teams field not required. You would need to update the Field Configuration Scheme assigned to the project to include the new Field Configuration and apply it to the Sub-task issue type.

[Christian Macedo]

I can't do that because the field configuration does not allow the value 'Team' to be edited as it is locked. So I can't assign it to a new field configuration scheme.