Ticket procedure

From ENIGMA

Revision as of 15:10, 5 September 2013 by IsmAvatar (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

A formal procedure for the life of a bug ticket is as follows:

Note that, as a small team, we do not have the resources to follow this formal procedure. We do not have nearly enough people to fill all the roles, and even if we did, the people we have are all volunteers, meaning they are under no obligation to fulfill their role, let alone to fulfill it in a reasonable time frame. Because of this, much of this process is expidited as much as possible, compressing several steps, and creating informal processes for these. Whatever the case, this formal procedure forms a guideline in what the procedure for a ticket *should* be, so that our informal processes may reflect this as best is possible with the resources we have.

Do realize that tickets and bugs do still fall through the cracks. To best expedite a ticket, we ask that reporters stick around and check up on the ticket throughout the life of the ticket, helping in whatever way they can. The reporter is also capable of closing their own tickets, should they feel they are invalid or resolved before the usual ticket process completes - that's perfectly fine. However, you are not required to close your tickets - they will follow their usual lifecycle and get closed off eventually anyways (hopefully by QA).

Personal tools
Namespaces
Variants
Actions
Navigation
ENIGMA
Other
Toolbox