ProCKSI

= Ticketing Policy =

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

General Definitions 1. '''Ticket Type'''BR ||'''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 ||'''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 ||'''Milestone'''||Planned version (future) || ||'''Version''' ||Released milestone (past)|| Tickets handling
Users need only to set the '''Ticket Type''' and the '''Version''' of software to which the ticket applies. The priority is optional and may be reassigned by one developers later. BR

Developers verify each ticket and on acceptance assign an '''Owner''', '''Priority''', '''Component''', and '''Milestone'''. If more information is needed than given in the original ticket description, its status should remain '''new''' until acceptance/refusal is possible.