Changes between Version 2 and Version 3 of TicketSpecs
- Timestamp:
- Feb 19, 2008, 2:00:14 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TicketSpecs
v2 v3 3 3 = Ticket Specs = 4 4 5 Reporting tickets can be very tricky if you are doing it for the first time. In some cases users unwillingly put to much or to little information about a bug or a new feature .5 Reporting tickets can be very tricky if you are doing it for the first time. In some cases users unwillingly put to much or to little information about a bug or a new feature and as a result the ticket handling process extends. That is why we have placed some recommendations about every ticket field to help you understand more about ticket reporting. 6 6 7 To help you understand more about ticket reporting at our developers site we have placed some recommendations about every ticket field below: 7 If you follow these recommendations you will help us to speed up the ticket handling process and in this way your request will be settled faster. 8 8 9 9 == Short summary == … … 13 13 === Examples === 14 14 15 IE: The sampleposteddata pages are not wrapping the "Value" col lumn15 IE: The sampleposteddata pages are not wrapping the "Value" column 16 16 17 17 Safari: objects are not selectable … … 28 28 29 29 - '''Task''' - tasks are usually used by FCKeditor core development team to specify "things that should be done" which aren't related to Bug and New Feature. So generally we don't recommend to use this type by reporters. 30 31 == Full description == 32 33 The '''Full description''' field is the most important field in creating a new ticket. Its content allows our team to know with what kind of problem the reporter is dealing with. There are a few tips that you should