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.
Updated by Etienne Massip over 10 years ago
- Category set to Custom fields
Updated by @ go2null over 10 years ago
My apologies - Hidden is not covered.
Updated by Arkhitech - More, Better, Faster! over 9 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.
Updated by Dipan Mehta over 9 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.
Updated by Toshi MARUYAMA over 9 years ago
- Related to Feature #13839: Custom fields presentation - Group custom fields in section / panel added
Updated by Alex Alex over 8 years ago
Updated by Christopher Caruk almost 8 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 [ ]| +-------------------------+
Updated by Johan Lichtjager over 7 years ago
I agree, this would mean a lot to me it this feature would be implemented. As redmine administrator I really dislike the use of fields called '-------' so my colleagues can group fields in an issue.... so here's a feed kick :-D
Updated by Sander Toonen over 7 years ago
+1 Any way in which we can group or visually organise the fields would be a major improvement. When you have about a hundred custom fields on a single tracker this is a must have.
Updated by Stephane Evr about 7 years ago
+1 This would also useful to stick some custom fields to a particular column so a given custom field will always be found at the same place hence the issue will be more readable.
Updated by Hide MATSUTANI almost 7 years ago
+1 If this feature is implemented, it is possible for me to apply various situations.
Updated by Laurent Girard almost 7 years ago
Updated by Daniel N almost 7 years ago
Updated by Shinji Tamura almost 7 years ago
Updated by Michael Schaefer almost 7 years ago
Updated by ale dp about 6 years ago
Updated by Marat I about 4 years ago
Updated by Lalu Ahirwar about 4 years ago
Updated by Karel Reznicek almost 4 years ago
related also to this: #24766
Updated by Yury Zhukovskiy over 3 years ago
Updated by Mischa The Evil almost 2 years ago
- Related to Feature #35281: [Meta] (Issues) Custom (and Standard) Fields Grouping and Positioning added