TicketingPolicy » History » Version 6

Anonymous, 07/04/2007 03:04 PM

1 1 Anonymous
= Ticketing Policy =
2 1 Anonymous
3 3 Paweł Widera
This page describes how '''Users''' and '''Developers''' should use the ticketing system:
4 1 Anonymous
5 4 Anonymous
6 1 Anonymous
== General Definitions ==
7 1 Anonymous
8 4 Anonymous
===  Ticket Type ===
9 4 Anonymous
Describes the nature of a new ticket.
10 1 Anonymous
11 2 Anonymous
  ||'''Defect''':      ||Anything that does not work as expected||
12 1 Anonymous
  ||'''Enhancement''': ||An improvement over an existing feature||
13 2 Anonymous
  ||'''Request''':     ||A new feature that should be added||
14 1 Anonymous
  ||'''Task''':        ||Anything that does not fall into the categories above||
15 1 Anonymous
16 4 Anonymous
=== Priority ===
17 4 Anonymous
Describes the order in which the ticket should be dealt with.
18 1 Anonymous
19 1 Anonymous
  ||'''blocker''':  ||Reduced functionality of parts of the system or the entire system until problem is fixed||
20 1 Anonymous
  ||'''critical''': ||Security breach or severe loss of data due to the defect|| 
21 1 Anonymous
  ||'''major''':    ||Defect with major impact '''OR''' big enhancement||
22 1 Anonymous
  ||'''normal''':   ||Defect with normal impact '''OR''' medium enhancement||
23 1 Anonymous
  ||'''minor''':    ||Defect with minor impact '''OR''' small enhancement||
24 1 Anonymous
  ||'''trivial''':  ||Defect with little or no impact '''OR''' cosmetic enhancement||
25 1 Anonymous
26 4 Anonymous
=== Versioning ===
27 6 Anonymous
Describes conventions for naming milestones and versions.
28 1 Anonymous
29 1 Anonymous
  ||'''Milestone'''||Planned version (future)  ||
30 4 Anonymous
  ||'''Version'''  ||Released milestone (past) ||
31 1 Anonymous
32 6 Anonymous
'''Milestones''' are named according to the next '''Version''' number.[[BR]]
33 6 Anonymous
'''Keywords''' can be added to specify a special purpose of a '''Milestone'''/'''Version''', e.g. "usability", "performance"
34 1 Anonymous
35 6 Anonymous
36 4 Anonymous
== Ticket Handling ==
37 1 Anonymous
38 1 Anonymous
=== Opening new Tickets ===
39 6 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. [[BR]]
40 4 Anonymous
41 6 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.
42 4 Anonymous
43 5 Anonymous
44 5 Anonymous
=== Referring to Tickets ===
45 5 Anonymous
Tickets can be referenced in the following way:[[BR]]
46 5 Anonymous
47 5 Anonymous
||Reference||!ticket:1, !issue:1, !bug:1, !#1
48 5 Anonymous
49 5 Anonymous
50 5 Anonymous
=== Closing and Referencing Tickets ===
51 4 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:[[BR]]
52 4 Anonymous
53 4 Anonymous
{{{COMMAND list-of-tickets}}}
54 4 Anonymous
 
55 1 Anonymous
||{{{COMMAND}}}   || close | closed | closes | fix | fixed | fixes ||
56 5 Anonymous
||                || references | refs | addresses | re | see ||
57 4 Anonymous
||list-of-tickets || !ticket:1, !ticket:2, ...      ||
58 1 Anonymous
||                || !ticket:1 & !ticket:2 & ...    ||
59 1 Anonymous
||                || !ticket:1 and !ticket:2 and ...||
60 5 Anonymous
61 5 Anonymous
'''Example:'''[[BR]]
62 5 Anonymous
The following example will close tickets !#10 and !#12, and add a note to ticket !#12.
63 5 Anonymous
64 5 Anonymous
{{{Changed blah and foo to do this or that. Fixes #10 and #12, and refs ticket:12.}}}