Changes between Version 14 and Version 16 of Ticket #2464
- Timestamp:
- Jun 14, 2007, 10:46:07 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2464
- Property Cc added
-
Ticket #2464 – Description
v14 v16 1 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 Then, as an advanced case, instead of being an all or nothing situation, the possible content of one field could be dependent on the ticket state: see #1299, #2752 and [#comment:13]. 4 2 5 3 6 === Use cases === … … 7 10 This might add just the flexibility required for complying with existing development processes. 8 11 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. 12 See also duplicates: #4028, #4643 9 13 10 14 ==== Hide the ''Keywords:'' field ====