Redmine

Visibility is covered in Issue #8050 due in 2.1.0

The grouping part I don't know about.

My apologies - Hidden is not covered.

+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.

+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.

+1

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    [            ]|
+-------------------------+

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

+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.

+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.

+1 If this feature is implemented, it is possible for me to apply various situations.

+1

+1

+1

+1

+1

+1

+1

+1
related also to this: #24766

+1