Locking down the Project Category Field

[Steven Janvrin]

Hello - like many Jira installations we use the Project Category field to identify types of Jira projects. We exclusively use this field for Jira administrative purposes, but recently we've found some users are adding this field to their JQL filters. Given that we change project categories values based on administrative requirements, this can and does break user filters.

Does anyone know if we can make the Project Category field "invisible" to user JQL filters?

Regards - Steve Janvrin / DTCC Jira Product Owner.

[Ste Wright]

Hi @Steven Janvrin 

I haven't seen this done natively, it might be possible using a scripting app - such as Scriptrunner or PowerScripts?

An alternative would be to either...

• Store the administrative tracking elsewhere, or...
• Visualise each Category's ID somewhere to be used in JQL (eg. category = 10003) - the ID is static unlike the name, so the filters would still work even if the name itself was changed

Ste

[Danny]

Ste is correct, it becomes an education and comms tasks for your Jira admins and champions to demonstrate how users can reference the category ID rather than the category name. This would reduce the impact to user filters considerably.  

[John Funk]

Hi Steven,

Unfortunately, I don't believe you are going to be able to lock that down or hide it. You should create a new custom field that you have more control over and use that. But you won't be able to do that at the Project level without some type of add on. 

[Juan Carlos Pin]

Hi @Steven Janvrin  

Check in the Settings / Issue Settings / Fields config / In the scheme you're using, if it can be hidden. (Mine is Locked)

Thx