Optional fields in tickets — at Version 10
|Reported by:||Owned by:||Christian Boos|
|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:|
Description (last modified by )
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.
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