ProCKSI

= Ticketing Policy =

This page describes how '''Users''' and '''Developers''' should use the ''trac'' ticketing system:

General Definitions 1. '''Ticket Type'''BR
Describes the nature of a new ticket. ||'''Defect''': ||Anything that does not work as expected|| ||'''Enhancement''': ||An improvement over an existing feature|| ||'''Request''': ||A new feature that should be added|| ||'''Task''': ||Anything that does not fall into the categories above|| 2. '''Priority'''BR
Describes the order in which the ticket should be dealt with. ||'''blocker''': ||Reduced functionality of parts of the system or the entire system until problem is fixed|| ||'''critical''': ||Security breach or severe loss of data due to the defect|| ||'''major''': ||Defect with major impact '''OR''' big enhancement|| ||'''normal''': ||Defect with normal impact '''OR''' medium enhancement|| ||'''minor''': ||Defect with minor impact '''OR''' small enhancement|| ||'''trivial''': ||Defect with little or no impact '''OR''' cosmetic enhancement|| 3. '''Versioning'''BR
Describes the difference between milestones and versions. ||'''Milestone'''||Planned version (future) || ||'''Version''' ||Released milestone (past)|| Users Policy
Users should only need to set the '''Ticket Type''' and, in case of a defect, the corresponding '''Version'''.BR Developers Policy
Developers are to evaluate the '''Content''', '''Type''', and '''Version''' of a ticket, and assign a '''Developer''', '''Priority''', '''Component''', and '''Milestone'''.