Difference between revisions of "Tickets"
(→Type) |
|||
| Line 29: | Line 29: | ||
! style="text-align:left;"| Value || style="text-align:left;"| Meaning | ! style="text-align:left;"| Value || style="text-align:left;"| Meaning | ||
|- | |- | ||
| − | |Defect || | + | |Defect || A bug |
|- | |- | ||
| − | |Enhancement | | + | |Enhancement | An improvement suggestion |
|- | |- | ||
| − | |Task || | + | |Task || Something that needs to be done that does not make any change to the code |
|} | |} | ||
| − | |||
===Milestone=== | ===Milestone=== | ||
Revision as of 04:15, 11 November 2014
(Draft)
Contents
Thoughts on how to manage tickets
This document is a work-in-progress.
Tickets have certain metadata, and more can be configured by the admin. We should decide what each of these means, and how we are going to use them.
Priority
| Value | Meaning |
|---|---|
| Optional | ? |
| Minor | ? |
| Major | ? |
| Critical | ? |
| Blocker | The component (or toolkit) cannot be used. We cannot release with a ticket in this state. |
Type
| Value | Meaning |
|---|---|
| Defect | A bug |
| An improvement suggestion | |
| Task | Something that needs to be done that does not make any change to the code |
Milestone
Version
Component
Keywords
State
| Value | Meaning |
|---|---|
| New | ? |
| Accepted | ? |
| Assigned | ? |
| Reopened | ? |
| Closed | (fixed, invalid, duplicate, wontfix, worksforme) |
| Review | ? |
| reviewed_ok | ? |
