<Field> can't be used in <team-managed project> because context has been removed.

[justin_lim]

I have custom fields that were created in a custom issue type (work type) in a team-managed project in Jira Cloud.

The fields appear to be able to be selected and populated correctly. However, under Project Settings / Fields, the list of fields show all the customs fields with a warning logo and in clicking the ellipses, a warning/error message states:

" <FieldName> can't be used in <ProjectName> because the context has been removed.". It then provides two options: "Add the global context to this field to use it in this project. " and "Remove field from project."

What is the cause of this error/warning? My understanding was global context was not required for custom fields in team-managed projects? The fields seem to work OK but will this cause other issues down the road? Thanks

[Manoj Gangwar]

Hi @justin_lim Welcome to the Community!

In a team-managed project, you can use the fields in a global context instead of a project-level context.

To create a field context in Jira, go to Issues > Custom fields, select the desired field, choose Contexts and default value, then click Add new context, specify the context details (label, description, applicable issue types, and projects), and then click Add
https://support.atlassian.com/jira-cloud-administration/docs/configure-custom-field-context/

[justin_lim]

Hi Manoj, thanks for your reply. In this case the fields are not visible under the Gear Icon > Issues > Fields > Custom Fields. I think this is because the team-managed custom fields created are not global fields but only associated with custom Work Types created within the team-managed project, so are confined to within the project.

Is there a way to add context in this case, to custom fields created locally within a team-managed project?

Thanks in advance

[Manoj Gangwar]

Yes, you can add context to custom fields created locally within a team-managed project in Jira by configuring the field's context to be applicable to specific projects and issue types, or by making it a global context.

https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/

[justin_lim]

Thanks for your reply. It looks like I have to make it global context. Strangely I created a sandbox team-managed project with custom field and the sandbox field does not show the warning message. I am not sure what the difference between the two though.