Hi, 
An additional factor that makes this issue so important: 
The 'Create linked issue' screen will ONLY show REQUIRED fields based on the Field Configuration. 

So this work-around is not a complete work-around, because Users will not be able to Create a linked issue, because the Create linked issue screen will NOT show the Team field because it is NOT required in the field configuration, while the creation WILL block the user and show the error that a required field is not filled in. 

This is a very silly outcome for the user. And it blocks work entirely. 

See: 

1. JSDCLOUD-3917 and 
2. JRACLOUD-60483

Hi all,

I'm April, a product manager with Atlassian Teams 👋.

I appreciate you sharing your insights and use cases regarding this topic around making the teams field required. We recognise the importance of this and plan to hopefully explore this further in the upcoming year. 

I'm keeping this in the 'gathering interest' phase - it's not a part of our official roadmap and is still in the early stages but is something that is on our radar.

Feel free to reach out in the comments if you have any questions about Teams. I will endeavour to provide an update next year on the status of this feature request. 

Best regards,

April

Can you please just make it possible? It's not a huge change...

Please work on improving Jira and not only working on new product. 
This kind of missing feature to not being able to put some field required is not normal. 

This issue has recently become even more problematic.

To overcome the fact that the "Team" field cannot be set as required in the Fields Configuration we set up a Workflow validation rule.
The rule requires the field to be populated when a new Jira Issue is created.

This is now causing issues on the creation of new Issues from the Epic view.
Previously, when someone tried to create an Issue from the Epic view, a screen popped up asking for additional details.
This allowed us to add the "Team" field and create the issue.

Since a couple of weeks ago, this stopped working.
Instead of having this popup screen we get an error message and we can't create the Issue.

The workaround won't let users easily create child issues within an epic anymore.

Team field need to be available in Field configuration schemes, so we can make it required properly.

If any of you set it as a validator in Workflows, keep in mind that sub-tasks are taking the team of their parent, so you will need a separated workflow for sub-tasks without the Team validation  

Now I cannot attach a screenshot here either. @Kavi Lai. I am alerted the error message: "You do not have permission to create attachments for this issue." 

Dear Atlassian Team, even the suggested work-around here does not work for me as the "Team" field is nowhere on that list with possible fields for "Field Required Validator", see the screenshots:

We also stumbled upon this and it was a major obstacle. Is there any technical and logical explanation why Atlassian decided to lock this field up? I'd be happy to learn more. We definitely need this field to be configurable. It should be possible to be made required.