Edgewall Software

Opened 3 years ago

Closed 22 months ago

Last modified 22 months ago

#10320 closed enhancement (duplicate)

grouping ticket fields

Reported by: fbrettschneider@… Owned by:
Priority: normal Milestone:
Component: general Version: 0.12.2
Severity: normal Keywords:
Cc: ryano@…
Release Notes:
API Changes:


Please, implement grouping of ticket fields in a way that just the standard fields are displayed by default, and additional groups of fields must be shown by clicking on an expand button "+".

Background: If one clicks "New Ticket" here, the form is very crowded with fields and therefore unclear since I installed quite a lot of plugins, mainly wiki:PluginList#ProjectTimeManagementTicketSystemExtensions. Most such additional ticket fields are maintained by the project leader and read by developers sometimes, but often new tickets are created and also later digged by the customer support team.

The problem: E.g. the customer support team grumbles about the overcrowded form and claims they are just interested in a few ticket fields, actually the standard fields. On ticket creation, or later when querying the ticket database, people don't want to see the timing/planning fields.

Attachments (0)

Change History (6)

comment:1 Changed 3 years ago by fbrettschneider@…

This is somehow related to #10326

comment:2 Changed 2 years ago by anonymous

By default, some field groups should be 'opened', some should be 'closed', and which ones depends on certain user groups (and those user groups must be defined somewhere).

http://trac-hacks.org/wiki/SimpleTicketPlugin is not sufficient because it doesn't give the possibility to expand hidden fields by "+" button.

comment:3 Changed 2 years ago by Ryan J Ollos <ryano@…>

I like some of the ideas in this ticket (collapse a set of ticket fields or hide them entirely for some particular users), and it seems to fit well with Trac's goal of being minimalistic and easy to use. th:SimpleTicketPlugin is being deprecated in favor of th:DynamicFieldsPlugin. See th:#9572:comment:4 for more info. This might be an appropriate enhancement request for the th:DynamicFieldsPlugin.

comment:4 Changed 22 months ago by fbrettschneider@…

Meanwhile we solved it here by this new trac-hacks plugin: wiki:GroupTicketFieldsPlugin

comment:5 Changed 22 months ago by cboos

  • Resolution set to duplicate
  • Status changed from new to closed

Note that this is a variation on #2464.

comment:6 Changed 22 months ago by Ryan J Ollos <ryano@…>

  • Cc ryano@… added

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

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

Note: See TracTickets for help on using tickets.