As soon as your JIRA Instance defines a complex configuration, the number of Custom Fields combined with the number of different Project Types will cause a very large View Field Configuration screen.
When you will access the View Field Configuration screen :
All System and Custom Fields are displayed, even if they are or not marked as Visible,
For each of this Fields, the screens where it is used will be listed,
Graphical enhancement in order to simplify the way to navigate in list of Fields
Some additional operation to help you in the configuration.
On this page:
Enhancements
Graphical enhancements
It concerned the ability ...
to apply a grayed font on Fields which are not visible in the Field Configuration
to provide an Expand/Collapse feature for each Fields,
and also to allow to hide all unused fields
Sample :
In the example (on the left side) with a JIRA Instance 5 Projects, 8 Workflows, 86 Custom Fields and 31 Screens, the gain in scrolling is important :
When all Fields are expanded, we have to scroll on 11 screens,
When Field details are collapsed, we have to scroll on 7 screens,
When Field details collapsed and only relevant Fields are displayed, we have to scroll on 5 screens,
Imagine the gain with more complex JIRA Instances.
But before all, it will allow you to have a clear definition of Field Configuration.
Expanded
Collapsed
Collapsed & Hidden
Additional Operation
When the Field Configuration page is loaded, an extra operation is added for each fields :
Hide in others operation allows you to hide the field in all others Field Configuration excepted the current one.
Take care ... If your instance has a too large number of Field Configuration, the request of this operation may fall in timeout. In such case, you will have to follow the result in your log files (Activate in Logging and Profiling page the class com.alkaes.admin.rest.field.FieldLayoutResource).
Example : For more than 100 Field Configurations with 500 Fields, the operation takes more than 30 min.
Note that you can use the same operation directly in pure REST (See API for Fields Configuration). It will allow you to use more specific restrictions and also request by example to hide a set of Fields in all Field Configurations excepted in set of them.