Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Should I hide unused fields in the Field Configuration?

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.

1 answer

1 accepted

0 votes
Answer accepted

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

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

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

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")

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

☕️ Monday coffee with Jexo: Weekly Atlassian news roundup | 21st June 2021

Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...

65 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you