Changes between Version 20 and Version 21 of TicketSpecs
- Timestamp:
- Aug 31, 2010, 9:49:52 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TicketSpecs
v20 v21 62 62 63 63 === Priority === 64 This option is usually disabled for reporters. It allows us to segregate the most important issues from the least important ones. 64 65 65 This option allows us to segregate the most important issues from the least important ones. 66 67 We recommend the to set the priority to '''Normal''' and not to use the '''High''' and '''Low''' options. Of course it is a very important for us to know what Bugs/New Features we should deal with firstly. That is why every ticket is reviewed by someone from the core development team, who sets its priority due to its importance. 66 By default, the priority is set to '''Normal'''. The '''High''' and '''Low''' options are set after new issue is confirmed, to know what Bugs/New Features we should deal with firstly. That is why every ticket is reviewed by someone from the core development team, who sets its priority due to its importance. 68 67 69 68 === Milestone === 70 71 This option is used by the core development team for targeting Bugs and New Features. So for example, if we have confirmed a bug and someone has began fixing it, we set the Milestone to specify what version will be free of this bug e.g. 'CKEditor 3.5'. We recommend no to use this option by reporters and leave this setting for developers.69 This option is disabled for reporters. Even if enabled, we recommend no to use this option by reporters and leave this setting for developers. 70 Milestone option is used by the core development team for targeting Bugs and New Features. So for example, if we have confirmed a bug and someone has began fixing it, we set the Milestone to specify what version will be free of this bug e.g. 'CKEditor 3.5'. 72 71 73 72 === Component === … … 135 134 ---- 136 135 137 === Assigned to === 138 139 This field is used by the development team to specify who will fix the bug or who will handle a new feature. We recommend reporters '''not to use this field''' at all. This field should be only used to gain information about the tickets status. So if you see that a ticket has been assigned it means that someone has began working with it. 136 === Assign to === 137 This option is ''disabled'' for reporters. It is used by the development team to specify who will fix the bug or who will handle a new feature. We recommend reporters '''not to use this field''' at all. This field should be only used to gain information about the tickets status. So if you see that a ticket has been assigned it means that someone has began working with it. 140 138 141 139 == Attachments ==