Changes between Version 1 and Version 2 of APP_BUG_REPORT_FORM_R0

Timestamp:

01/10/09 08:47:48 (16 years ago)

Author:

deyan

Comment:

--

APP_BUG_REPORT_FORM_R0

@@ -3 +3 @@
 [[TicketQuery(summary=APP_BUG_REPORT_FORM_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]
 = Analysis =
-^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^
-
 == Overview ==
-^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
-
+{{{
+this should be invokable  from help menu, or on internal error
+}}}
+The Bug report form eases communication between users and developers. The form contains:
+ * A log containing information useful for debugging. This field is read only.
+ * A custom text field containing user explanation on what happened. This is not a required field.
+ * A warning that user information such as working path and filenames will be sent.
 == Task requirements ==
 ^(Necessary requirements that the task must fulfill.)^
 
 == Task result ==
-^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^
+Code.
 
 == Implementation idea ==