Use full width for custom textarea fields, and make them collapsible

[anonymous]

The content of custom textareas might get very big, so it would be better to place these fields in full width after description field.

Furthermore it would be nice, if these fields are collapsable, so you could close them, if you do not need them at the moment.

[franz.mayer@…]

possible solution of this ticket

[franz.mayer@…]

sample screenshot of attached implementation

[Remy Blank]

I don't think moving the textarea fields below the description is a good idea in general, as the description itself can become quite long as well (and that case is much more likely in the installations I know of).

Making the sections collapsible is a good idea, though, and they should use the full width of the ticket, instead of being indented by the field label.

[franz.mayer@…]

Replying to rblank:

I don't think moving the textarea fields below the description is a good idea in general, as the description itself can become quite long as well (and that case is much more likely in the installations I know of).

When creating or editing a ticket the textarea fields are also below the description field. So for me (and my collegues) it is more consistent, when the custom text fields are printed below then in preview / ticket view.

Making the sections collapsible is a good idea, though, and they should use the full width of the ticket, instead of being indented by the field label.

I tried to make the Description field also collapsible, but I wasn't able to place the arrow correctly (and it dind't work either). When the Description field is collapse it is no disadvantage when description is longer and you would like to see any custom ticket, because you can then simply collapse description.

[franz.mayer@…]

When discussion positions of fields, I forgot to say that in my company the best order of fields when entering (creating, modifying a ticket) would be:

1. Summary
2. all one-line fields (such as milestone, version, simple custom fields, etc.)
3. Description
4. all textarea custom fields

This is also the printing layout (except textarea custom fields for now), so it would be more consistent (and thus more intuitive).

[Christian Boos]

Well, we currently have the possibility to order the custom fields, and we wanted to extend that so it would be possible to specify the order for all fields, default (including description) and custom alike (#4549, even #6280 it seems).

[framay <franz.mayer@…>]

possible solution of this ticket with original ordering of textarea elements

[framay <franz.mayer@…>]

I added a possible solution of this ticket with original ordering of textarea elements (t10381-ticket_box.html.diff​ - diff from rev 11317) The textarea elements are foldable as in previous patch.

[Ryan J Ollos]

#10834 closed as a duplicate, requesting that all textareas be foldable.

[Franz Mayer <franz.mayer@…>]

Replying to rjollos:

#10834 closed as a duplicate, requesting that all textareas be foldable.

I don't see any request regarding folding textareas in ticket #10834.

[Ryan J Ollos]

Typo, #10843.

[Ryan J Ollos]

See also #9073, which suggests implementing a collapsible class.