Version 2 (modified by Wojciech Olchawa, 15 years ago) (diff)


Table of Contents

  1. Short summary
    1. Examples
  2. Type

Ticket Specs

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.

To help you understand more about ticket reporting at our developers site we have placed some recommendations about every ticket field below:

Short summary

In this field the reporter should place a short summary about the ticket. If possible the reporter should put the name of the browser in which a new bug has occurred or in which a new feature is requested, in the beginning of the summary. Of course if the reported problem is found in every browser you don't have to put anything in the beginning of the field.


IE: The sampleposteddata pages are not wrapping the "Value" collumn

Safari: objects are not selectable

FF3 : Content "flashing" on load


This field is used for choosing the type of the ticket. You can choose from:

  • Bug - if you found that something isn't working properly in FCKeditor or in our other projects
  • New Feature - when you want to make a request for something new to be added to any of our project
  • 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.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy