TicketingPolicy » History » Version 9

Anonymous, 07/04/2007 03:47 PM

1 1 Anonymous
2 9 Anonymous
h1. Ticketing Policy
3 1 Anonymous
4 4 Anonymous
5 9 Anonymous
This page describes how *Users* and *Developers* should use the ticketing system:
6 1 Anonymous
7 1 Anonymous
8 1 Anonymous
9 9 Anonymous
h2. General Definitions
10 1 Anonymous
11 7 Anonymous
12 1 Anonymous
13 9 Anonymous
h3.  Ticket Type
14 1 Anonymous
15 9 Anonymous
Describes the *nature* of a new ticket.
16 1 Anonymous
17 9 Anonymous
  ||*Defect*      ||Anything that does not work as expected||
18 9 Anonymous
  ||*Enhancement* ||An improvement over an existing feature||
19 9 Anonymous
  ||*Request*     ||A new feature that should be added||
20 9 Anonymous
  ||*Task*        ||Anything that does not fall into the categories above||
21 1 Anonymous
22 1 Anonymous
23 9 Anonymous
h3. Priority
24 1 Anonymous
25 9 Anonymous
Describes the *importance* of a ticket and the *order* in which it should be dealt with.
26 1 Anonymous
27 9 Anonymous
  ||*blocker*  ||Reduced functionality of parts of the system or the entire system until problem is fixed||
28 9 Anonymous
  ||*critical* ||Security breach or severe loss of data due to the defect|| 
29 9 Anonymous
  ||*major*    ||Defect with major impact *OR* big enhancement||
30 9 Anonymous
  ||*normal*   ||Defect with normal impact *OR* medium enhancement||
31 9 Anonymous
  ||*minor*    ||Defect with minor impact *OR* small enhancement||
32 9 Anonymous
  ||*trivial*  ||Defect with little or no impact *OR* cosmetic enhancement||
33 1 Anonymous
34 1 Anonymous
35 9 Anonymous
h3. Versioning
36 1 Anonymous
37 9 Anonymous
Describes conventions for *naming* milestones and versions.
38 1 Anonymous
39 9 Anonymous
  ||*Milestone*||Planned version (future)  ||
40 9 Anonymous
  ||*Version*  ||Released milestone (past) ||
41 1 Anonymous
42 9 Anonymous
*Milestones* are named according to the next *Version* number.
43 9 Anonymous
44 9 Anonymous
*Keywords* can be added to specify a special purpose of a *Milestone*/*Version*, e.g. "usability", "performance"
45 9 Anonymous
46 9 Anonymous
47 9 Anonymous
48 9 Anonymous
h2. Ticket Handling
49 9 Anonymous
50 9 Anonymous
51 9 Anonymous
52 9 Anonymous
h3. Opening new Tickets
53 9 Anonymous
54 9 Anonymous
Users only need to set the *Ticket Type* and the *Version* of the software to which the ticket applies. The *Priority* is optional and may be reassigned by one of the developers later. 
55 9 Anonymous
56 9 Anonymous
57 9 Anonymous
Developers verify each ticket and, on acceptance, assign an *Owner*, *Priority*, *Component*, and *Milestone*. If more information than given in the original ticket description is needed, its status should remain as *new* until acceptance/refusal is possible.
58 9 Anonymous
59 9 Anonymous
60 9 Anonymous
61 9 Anonymous
h3. Referring to Tickets
62 9 Anonymous
63 9 Anonymous
Tickets can be referenced in the following way:
64 9 Anonymous
65 9 Anonymous
66 9 Anonymous
||Reference||!#1, !issue:1, !bug:1, !#1
67 9 Anonymous
68 9 Anonymous
69 9 Anonymous
70 9 Anonymous
h3. Closing and Referencing Tickets
71 9 Anonymous
72 9 Anonymous
Tickets should not be closed by hand, but automatically when committing the code changes to the SVN repository, referring to the ticket numbers as follows:
73 9 Anonymous
74 9 Anonymous
75 9 Anonymous
<pre>
76 1 Anonymous
 
77 9 Anonymous
<pre>
78 4 Anonymous
||                || references | refs | addresses | re | see ||
79 9 Anonymous
||list-of-tickets || !#1, !#2, ...      ||
80 9 Anonymous
||                || !#1 & !#2 & ...    ||
81 9 Anonymous
||                || !#1 and !#2 and ...||
82 5 Anonymous
83 9 Anonymous
*Example:*
84 9 Anonymous
85 5 Anonymous
The following example will close tickets !#10 and !#12, and add a note to ticket !#12.
86 1 Anonymous
87 9 Anonymous
<pre>