Edgewall Software

Opened 15 years ago

Last modified 3 years ago

#2464 new enhancement

Conditional fields in tickets — at Version 14

Reported by: johan.regnell@… Owned by: Christian Boos
Priority: normal Milestone: next-major-releases
Component: ticket system Version: 0.9.2
Severity: major Keywords: tracobject tickettype conditional custom field
Cc: hw@…, erikand@…, sam@…, mark.dodgson@…, dartar@…, ryan@…, hans.westerveen@…, colin.white@…, mmitar@…, itamarost@…, admiralnemo@…, sam.halliday@…, martin.wagner@…, Ryan J Ollos, leho@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Christian Boos)

Not necessarily all possible fields should be presented to the user. There could be preconditions attached to fields, for checking if they're applicable at all and for checking if the current user can actually set/modify them.

Use cases

Ability to have different ticket fields for different ticket types

(original one) When using quite different types of tickets (bug-report, requirement, etc), there is a need for different fields depending on the ticket type. This might add just the flexibility required for complying with existing development processes. Great feature in particular when support for master and child tickets is planned, trac could be more of a requirements management system beyond the issue database approach.

Hide the Keywords: field

See #3281

Hide some fields for new tickets

See #1580. This could be achieved quite simply by putting the ticket id in the condition.

Change History (14)

comment:1 by Christian Boos, 15 years ago

Keywords: tracobject tickettype added
Owner: changed from Jonas Borgström to Christian Boos

Yes, that was one of the early request concerning the TicketTypes feature. Having more flexibility for the ticket properties would be nice.

There's still the open question of the UI, though: As you have to select the type of a ticket, you don't know beforehand which type specific fields you'd need.

One solution to this would be to have only the "common" fields at ticket creation type, and the "type specific" ones when editing the ticket.

Same problem when changing the ticket type, how to handle the type specific fields? Maybe when the type changes, only take into account the type change itself, possibly some changes for the common fields, and ignore any type specific field change. The type specific fields of the new type will be available for a second round of edit, after the type change has occurred.

comment:2 by pkou at ua.fm, 15 years ago

First of all, I would propose to allow the "type specific" fields for custom fields only. The suggestion is to show/hide "type specific" fields using JavaScript:

  • By default, all fields are shown;
  • When the page has loaded, fields for non-default type are hidden;
  • When the ticket type is changed, fields for non-selected type are

hidden, fields for the selected type are shown. This would cause layout problems that can be resolved in one of the following ways:

  • Apply new layout to the "type specific" fields when they are shown or


  • Consider "type specific" fields as groups of fields. Layout groups

separately. Show active groups and hide other groups when the ticket type is changed. The approach could work for browsers that do not support JavaScript. I do not think that changing a field that does not belong to currently selected type is an issue.

comment:3 by anonymous, 15 years ago

Cc: shishz@… added

comment:4 by Christian Boos, 14 years ago

Milestone: 1.0

#4028 marked as duplicate.

I'll soon attach here a patch going in that direction.

comment:5 by anonymous, 14 years ago

Cc: mr@… added

comment:6 by anonymous, 14 years ago

Cc: hw@… added; shishz@… mr@… removed

comment:7 by anonymous, 14 years ago

#4643 marked as duplicate.

comment:8 by anonymous, 14 years ago

Cc: erikand@… added

I want to listen in on this..

comment:9 by Christian Boos, 14 years ago

Keywords: conditional custom field added

I just closed #2752 as duplicate. That ticket was not about the type field, but about the component, but I think a generic solution could be worked out (see last comment on that ticket).

comment:10 by Christian Boos, 14 years ago

Description: modified (diff)
Summary: Ability to have different ticket fields for different ticket typesOptional fields in tickets

comment:11 by Christian Boos, 14 years ago

Summary: Optional fields in ticketsConditional fields in tickets

comment:12 by Christian Boos, 14 years ago

#1299 would be an other use case, slightly extended: instead of an all or nothing approach (the field is present or missing), its content could depend on other fields (in this case, the list of available components would depend on the selected milestone).

comment:13 by sam@…, 14 years ago

Cc: sam@… added

I'm keen to get this feature implemented, and I'm starting to learn enough about Trac and Python to get it implemented. I'm keen to get feedback on this to increase the chance of a patch being accepted into the trunk.

Some requirements:

  • The ability to filter out fields based on ticket data: component, milestone, ticket type, component.
  • The ability filter out fields based on user permissions.
  • The ability to filter out standard, as well as custom, fields. For some tickets you don't want a description field, just the 1-line summary.

Configuration file:

  • Add [ticket-standard] as a complement to [ticket-custom], for manipulating built-in ticket fields.
  • (field-name).conditions will set up conditional restrictions
    • (field-name).conditions.(conditional-field) can be a | separated list in one of two formats
    • A|B|C - means only show this field when conditional-field is set to A, B or C
    • !A|B|C - means only show this field when conditional-field is not set to A, B or C
  • (field-name).conditions.permission operates similarly on the permissions that the current user has.

Example configuration:

description.conditions.type = !storycard
owner.condition.permission = TICKET_FULLACCESS

installation = select
installation.label = Select the affected installation
installation.condition.component = Frontend|Webservice
installation.condition.milestone = !alpha1|alpha2

Suggested implementation:

  • Whenever the ticket-details form is displayed, use the current, default, and get/post data to determine which fields to show.
  • Work out which fields are going to be linked to conditions. In the case above, this will be type, component, and milestone.
  • Add an onchange javascript-refresh that reloads the page, with all current field values loaded into the querystring.
  • Using ajax would be an optional enhancement

comment:14 by Christian Boos, 14 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.