Implementation of the ticket system

Registered by Vincent

The tickets will be the hearth of the projects, with the wiki. A ticket is a demand of an user to correct a defect, or to had a new function. Each ticket will have:
- a registrant;
- an assignee;
- a priority;
- a type (task, defect, enhancement);
- a status (opened, closed, won't fix, cannot reproduce, ...); it will be no difference between status and resolution;
- a component affected;
- a targeted milestone (optional);
- a summary and a description);
- a list of keywords (aka tags).

Tickets will receive comments (which are linked to changes to the ticket) and attachments, if needed.

Blueprint information

Status:
Started
Approver:
None
Priority:
Essential
Drafter:
None
Direction:
Needs approval
Assignee:
Vincent
Definition:
Approved
Series goal:
Accepted for 0.1
Implementation:
Needs Infrastructure
Milestone target:
milestone icon 0.1alpha
Started by
Vincent

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.