Changes between Version 2 and Version 3 of TicketSpecs


Ignore:
Timestamp:
Feb 19, 2008, 2:00:14 PM (12 years ago)
Author:
Wojciech Olchawa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketSpecs

    v2 v3  
    33= Ticket Specs =
    44
    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.
     5Reporting 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.
    66
    7 To help you understand more about ticket reporting at our developers site we have placed some recommendations about every ticket field below:
     7If 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.
    88
    99== Short summary ==
     
    1313=== Examples ===
    1414
    15 IE: The sampleposteddata pages are not wrapping the "Value" collumn
     15IE: The sampleposteddata pages are not wrapping the "Value" column
    1616
    1717Safari: objects are not selectable
     
    2828
    2929- '''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
     33The '''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
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy