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

Justin Lim_egbz3j

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

 

Theo Swartz

A user I'm working with encountered the same warnings about context being removed. In his case, it actually does cause an issue because the warning prevents the warned user from using or editing those fields. I'm surprised that you were still able to use the fields after Jira said that they were "unable to be used".

Something I have yet to understand is: Why does Jira allow users to create custom fields from within the project context instead of the global context, if errors will appear and (either warn against using or outright) prevent them from further use of the fields in the project?

My affected user also had no issues using custom fields in his project which were created in the project context - until all of a sudden about two weeks later, usage stopped being possible and the errors OP described appeared. Does anyone happen to understand this behavior of Jira?