Should I hide unused fields in the Field Configuration?

[Sangjun Jeon]

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.

[Nic Brough -Adaptavist- · Accepted solution]

Heh, not a chance, directly.  You will need to do one of two things:

1) Find or write a (potentially horried) JQL function to enable this searching.  I've seen a couple that try to do it, and most of them fall over spectacularly when there's a lot of data to work with, so I can't recommend them.

2) Find or write a field that gathers the information.  The best way to do that is a scripted field, as that is updated on every comment/update and hence doesn't load the system in any significant way.  There's a really good one built into the JIRA Toolkit which is a really good starting point, although it is hard coded.  The "Participants" field in there gives you "Current assignee, reporter and anyone who has commented" all in a simple multi-user-picker field.  Makes searching a doddle (and reporting is quite handy - something the JQL function can't help you with!)

[Ignacio Pulgar]

Thank you so much, Nic!

[Asael Sepúlveda]

Have you tried with "comment ~ currentUser()"?

[Ignacio Pulgar]

Hi, Asael. Yes, but that query returns just comments in which currently logged in user has been mentioned, and not the issues in which that user has added a comment. Anyway, it is useful for getting issues where currentUser()'s action might be needed.