As already mentioned by others: there is a huge, urgent need to filter Teams for certain context.

We are using Jira Service Management in different parts of the organisation: HR, IT, facility management. When triaging issues, I need to be able to filter the available Teams, as not all are relevant in every context.   

As 'Teams' becomes more impactful across the Atlassian suite we need 'Field Contexts' for filtering the many teams from other teams. For example, we need to only show 5/100 teams to our desktop team when they are assigning tickets to each other in an effort to prevent tickets/issues being assigned to the wrong department/team in a large multifunctional company.  

This feature would help us a lot on the "Description" field, as the suggested workarounds are not really helpful..

Please enable it as it is in DC!

Our org wants this for the Resolution field.  Configuring the inclusion of Resolution IDs in the workflow transition properties is burdensome and very prone to error, especially for instances with scores of workflows with one or more transitions resulting in the choosing of a Resolution subset.

On the Description field this is already available in DC so why not cloud? 

Ability to create project context for fields like "Description" allows us to provide project specific guidance while avoiding creation of new custom fields.

This will really help all Atlassian community, please implement this.

I would like this feature so that I can limit which Teams are displayed in the Team field dropdown depending on which Project you are in.

This is much needed for the Priority and Resolution fields. 

This feature would be especially useful for mergers & acquisitions, where importing another company's Jira data can bring in additional system field definitions not used by the acquiring company. We are battling this right now.