Where does the LOCKED custom field "Team" comes from?

[Moshe Azaria]

We have a custom field called "Team" that is LOCKED so I get that it comes from either Jira itself or one of it's plugins, but I need to know where it originates in order to workaround it and disable it.

Any help will be appreciated!

[Fabio Racobaldo _Herzum_ · Accepted solution]

Hi @Moshe Azaria ,

Team is a internal field provided by JIRA Software module and can not been disabled. Why do you need to disable it? You could remove that field from all screens.

Fabio

[Moshe Azaria]

Thanks @Fabio Racobaldo _Herzum_ , when I remove it from the screen, and try to create an issue, I get an error that this field is must be filled. (although it's not associated with the only screen it was attached to.

[Fabio Racobaldo _Herzum_]

Hey @Moshe Azaria , you need to make that field optional in the related Field Configuration associated to your project

[Moshe Azaria]

Again thank you @Fabio Racobaldo _Herzum_ , The field doesn't seem to be required, or am I missing something?

Could it be that because we have 2 such field "Team", it makes the LOCKED one required?

[Fabio Racobaldo _Herzum_]

You have another field Team defined as required in the field configuration. Please make it optional.

[Moshe Azaria]

  OK I see now. Is there a way to make it required to one project only?

Edit: found this: https://community.atlassian.com/t5/Jira-questions/How-do-you-make-Required-mandatory-fields-only-for-1-project/qaq-p/1289729#:~:text=project%20settings%20%3E%20workflow%20%2C%20edit%20the,an%20error%20message%20if%20desired.

I'll try it first. Thanks

[Fabio Racobaldo _Herzum_]

yes, you can do that defining a specific field configuration, setup a specific field configuration scheme and associate it to your single project