Changes between Initial Version and Version 10 of Ticket #2464
- Timestamp:
- Mar 14, 2007, 12:40:58 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2464
- Property Cc added
- Property Summary Ability to have different ticket fields for different ticket types → Optional fields in tickets
- Property Owner changed from to
- Property Milestone → 1.0
- Property Keywords tracobject tickettype conditional custom field added
-
Ticket #2464 – Description
initial v10 1 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. 2 3 === Use cases === 4 ==== Ability to have different ticket fields for different ticket types ==== 5 ''(original one)'' 1 6 When using quite different types of tickets (bug-report, requirement, etc), there is a need for different fields depending on the ticket type. 2 7 This might add just the flexibility required for complying with existing development processes. 3 8 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. 9 10 ==== Hide the ''Keywords:'' field ==== 11 See #3281