Changes between Version 6 and Version 7 of TracDev/Proposals/TicketTypes

Timestamp:

May 4, 2005, 9:14:25 AM (19 years ago)

Author:

pkou at ua.fm

Comment:

Proposal: Different custom fields depending on ticket type

TracDev/Proposals/TicketTypes

@@ -82 +82 @@
 in the database. It simply needs to be "activated" by using the {{{severity}}}
 command in {{{trac-admin}}}.
+
+== Other issues ==
+
+=== Different custom fields depending on ticket type ===
+By: ''pkou at ua.fm''
+
+It would be nice if different sets of custom fields are visible to end user when ticket type is changed.
+
+Rationale: Different ticket types can require different types of additional information that needs to be entered, for example:
+ * ''Event'': Due date, location;
+ * ''Enhancement'': Source, Benefit, Link to business case/requirement, Review status, Approval status, Links to specifications;
+ * ''Defect'': Customer ID
+ * ''Task'': ''No additional custom fields.''
+Hidden custom fields are initialized with zero/empty values.
+
+Standard fields represent common information that should be available in every ticket.
+
+Affected areas of functionality:
+ * When existing ticket is displayed, then unnecessary custom fields are hidden;
+ * When new ticket is created, then custom fields are displayed depending on selected ticket type.