Custom Field Groups, and User Specific Fields
This is just a suggestion but
It would be nice if we could group fields in issues. For example Standard Fields could have the fields Team Lead, and Project Number, User fields could have Root Cause and estimated time, while developer fields could have How to fix, Time required to fix etc.
It would be nice to be able to hide fields such as the developer fields from users such as QA or documentation users.
#4 Updated by Arkhitech - More, Better, Faster! over 7 years ago
+1 for this. Apart from visibility and hiding, there is a need to 'group' the custom fields.
This can be implemented by simply assigning a category field to the custom fields. Thus when custom fields are rendered, a block is formed based on category, and all custom fields in the category are shown within the block.
#5 Updated by Dipan Mehta about 7 years ago
+1. This is very useful when there are significant use of Custom-fields.
I think more important than the visibility is that we can have a nice layout on the issue page based on functional grouping (QA/Testing, planning, version control related, root-cause analysis, customer specific etc.) which is not possible right now.
#8 Updated by Christopher Caruk almost 6 years ago
Perhaps an easy way to do this would be to group by the first word in the custom field name. For example, Flight Date, Flight Reference, Flight Number would all render into a box called Flight:
+-- Flight ---------------+ | Date [ ]| | Reference [ ]| | Number [ ]| +-------------------------+