Edgewall Software
Modify

Opened 3 years ago

Last modified 20 months ago

#10381 new enhancement

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

Reported by: anonymous Owned by:
Priority: normal Milestone: next-major-releases
Component: ticket system Version: 0.12.2
Severity: normal Keywords:
Cc:
Release Notes:
API Changes:

Description

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.

Attachments (3)

ticket_box.html.diff (1.3 KB) - added by franz.mayer@… 3 years ago.
possible solution of this ticket
ticket_10381_custom_textarea.png (53.0 KB) - added by franz.mayer@… 3 years ago.
sample screenshot of attached implementation
t10381-ticket_box.html.diff (1.2 KB) - added by framay <franz.mayer@…> 20 months ago.
possible solution of this ticket with original ordering of textarea elements

Download all attachments as: .zip

Change History (8)

Changed 3 years ago by franz.mayer@…

possible solution of this ticket

Changed 3 years ago by franz.mayer@…

sample screenshot of attached implementation

comment:1 follow-up: Changed 3 years ago by rblank

  • Milestone changed from 0.13 to next-major-0.1X
  • Summary changed from Print custom textarea fields in full width (after description) to Use full width for custom textarea fields, and make them collapsible

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.

comment:2 in reply to: ↑ 1 Changed 3 years ago by 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.

comment:3 Changed 3 years ago by 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).

comment:4 Changed 3 years ago by cboos

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

Changed 20 months ago by framay <franz.mayer@…>

possible solution of this ticket with original ordering of textarea elements

comment:5 Changed 20 months ago by 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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new The ticket will remain with no owner.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.