Changes between Version 6 and Version 7 of TicketSubmissionGuide


Ignore:
Timestamp:
Aug 28, 2008, 3:56:47 PM (16 years ago)
Author:
Tim Kosse
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketSubmissionGuide

    v6 v7  
    8181== Submitting a ticket ==
    8282
    83 When you finally submit the ticket, be verbose in the description. Include every single detail that might be of importance.
     83This guide only covers '''what''' your ticket should contain. Read the [wiki:NewTicketFormGuide 'New ticket' form guide] '''how''' to fill out the 'new ticket' form.
     84
     85Your ticket should contain a verbose description of your issue. Include every single detail that might be of importance.
     86
     87You should '''include the full version number''' of FileZilla you are using in the ticket. If you don't enter a version number or are merely saying that you are using the ''latest version'', nobody will be able to figure out which version you were using a couple of months in the future.
     88
     89=== System details ===
     90
     91In your ticket, include the name and version of the operating system you are using. Also name your system's processor architecture.
     92
     93Examples:
     94
     95 * Windows Vista with SP6 on Intel Core i7
     96 * OS X 10.5.3 on PowerPC
     97 * Ubuntu Linux 9.6 on UltraSPARC
     98
     99=== Logs ===
     100
     101Especially with transfer related issues, valuable information is shown in the message log of FileZilla.
     102
     103 * '''Attach complete logs'''[[br]Snippets are useless without the surrounding context
     104 * '''Do not obfuscate logs'''[[br]]You will most likely destroy the important parts of the log if you attempt to obfuscate it
     105 * '''Set program language to English''' (client only)[[br]]FileZilla is available in over forty languages, but most developers can only read English.
     106 * '''Logging debug level''' (client only)[[br]]In the settings dialog, set the debug level to 3 to display a lot more additional information in the log. While not useful for most users, the developers can read and understand the debug information fluently.
     107
     108=== Screenshots ===
     109
     110If you have screenshots, attach them as simple .png files. Do not use .jpg and do not put screenshots into Word documents and the likes.
    84111
    85112== Summary ==