We have quite a lot of custom fields created for our project. There are some more useful than others, thus, we want those highly used fields to show up first than showing all (100+) on the custom field section. If not, can we eliminate some of fields from showing up?
Custom fields can be configured by project and issue type. So you can only show a field for certain projects or issue types within a project. For select lists and the like you can have a different set of values for each project or issue type. For instance, you may have aselect list field named Request Type. The values would be different if requesting work by the DBA group vs. software install to workstations. After you add the field click on it in the custom field list and use the add context option to use different lists by project/type. When defining the field you can select the project and issue types it is for. You can modify it later also.
Another option is to use tabs. the view screen always defaults to showing the items on the first tab. then organize the fields on other tabs. With that many fields I'm sure there is a logical way to organize them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The panel is a simple list that iterates through the fields in alphabetic order, there's no way to rearrange them.
You could edit the files that generate the list, and restart. I get around it by limiting fields to the projects that need them (in which case they only appear when a user has selected a relevant project) or even removing the searcher completely, but that means you cannot search on them at all, they become data items only
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well if we can limit the fields by the project they selected, that'd be great. Can you explain how you achieve this?
Thanks again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.