CUBRID Cluster Issue Tracking Tips
CUBRID Cluster JIRA Issue Tracker
Ticket types
| Issue Type | Description |
| defect | any defect including bugs. Defect is wider concept than bug |
| enhancement | function enhancement, performance enhancement, almost of modifications which are not defect but required. |
| task | not only implementation task, any kind of task, much general... |
| operation | doing operational task, e.g. up test environment. |
| design | no doubt |
| documentation | no doubt |
| specification | no doubt, this type of ticket will be assigned to spec owner |
| test | when we have something to test without product modification, for example, performance comparison... test from product modification will be covered with defect or enhancement types. |
| release | product release... Release Manager's role |
| review | code review and test review when no related ticket was presented |
Ticket title heading recommendation
- [Feature Request] or[FR]
- [Bug Report] or [Bug]. We need add milestone mark in Bug header. Such as:
- M1's bugs : [Bug][M1]
- M2's bugs : [Bug][M2]
- [Problem Report] or [PR]
- [Specification] or [Spec]
- [Task]
- [Code Review] or [CR]
- [Test Review] or [TR]
- [Design Review] or [DR]
Page info
viewed 306 times
![[Level:8]](http://www.cubrid.org/modules/point/icons/default/8.gif "Rank: 8/30, reputation score 558 (28% completed for the next level)"){kind=icon}
CUBRIDShare this article