nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Should I hide unused fields in the Field Configuration?

Sangjun Jeon_01sqbv

Hi.

I usually configure screens per project to show or hide fields.

So in the field configuration, there are all fields shown, even though they are not used.

Suddenly I am wondering that is it okay to leave the unused fields shown.

I am worried that is it possible to make it slow for the server performance.

When i try to hide all of unused fields, it may take very long time to apply.

Just I want to know what is the best practice about the field configuration.

Thank you so much in advance for your advice.

Accepted answers

Nic Brough -Adaptavist-

It does not make a lot of difference if you hide the fields.

All comments

Nic Brough -Adaptavist-

It does not make a lot of difference if you hide the fields.

Sangjun Jeon_01sqbv

I got it. Thank you so much.
Have a good day.

Steven McCaffrey

Do you see any performance benefits if you do this to all your field configurations?

Nic Brough -Adaptavist-

Nope. It makes some difference, of course, any processing change does, but nothing you will really notice.

Hiding a field in a field configuration does not have any significant effect. If you want to improve performance of custom fields, you will find it a thousand times more effective to reduce a field's context. (Or best of all, clamp down on "fielditis" - reduce the number of custom fields, share more, add fewer)

Changing if a field is on screen or shown/hidden in the field configuration has a trivial impact on performance - Jira looks at the config and shows it or not. The field is still there, with all its overhead in doing the config checks and the data in the index.

But if you remove a field's context from a project, that REALLY matters. There is less to be indexed, there is nothing there to even be checked for field configuration or screens. Reducing a custom field context is the second best thing you can do for performance (after fixing "fielditis")

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

jira-core