79 | | Note: There are two options in the list that regard to FCKeditor sister projects: '''FCKpackager''' and '''MediaWiki+FCKeditor''', so if you have a problem with them just choose this options. |
| 79 | '''Note''': There are two options in the list that regard to FCKeditor sister projects: '''FCKpackager''' and '''MediaWiki+FCKeditor''' so if you have a problem with one of them simply choose one of these options. |
| 80 | |
| 81 | === Version === |
| 82 | |
| 83 | This option allows the reporter to specify in which version of FCKeditor a bug occurred. If you have found a bug in two versions, remember to always choose the older version of the program. That way we can determine the origin of the bug. |
| 84 | |
| 85 | === Keywords === |
| 86 | |
| 87 | The "Keywords" field is a powerful and important feature. FCKeditor core development team uses it to gain information regarding a ticket, including browser details, current status and ticket quality. Someone our team always sets the keywords so we recommend the reporters '''not to use this field'''. |
| 88 | |
| 89 | The following is the list of standard keywords. The keyword name is always "PascalCased" with no spaces: |
| 90 | |
| 91 | {{{ |
| 92 | #!rst |
| 93 | |
| 94 | ================ ============================================================================= |
| 95 | **Browser Specific** |
| 96 | ---------------------------------------------------------------------------------------------- |
| 97 | **Firefox** (`[query:keywords~=Firefox Tickets]`:trac:) |
| 98 | Marks tickets that are related to Gecko compatible browsers only (not only |
| 99 | Firefox). |
| 100 | |
| 101 | **IE** (`[query:keywords~=IE Tickets]`:trac:) |
| 102 | Marks tickets that are related to Internet Explorer only. |
| 103 | |
| 104 | **IE7** (`[query:keywords~=IE7 Tickets]`:trac:) |
| 105 | Marks tickets that are related to Internet Explorer version 7.x only. |
| 106 | ---------------- ----------------------------------------------------------------------------- |
| 107 | |
| 108 | ---------------------------------------------------------------------------------------------- |
| 109 | **Core Developers Activity** |
| 110 | ---------------------------------------------------------------------------------------------- |
| 111 | **CantFix** (`[query:keywords~=CantFix Tickets]`:trac:) |
| 112 | Indicates that the ticket is looking for something that is almost impossible |
| 113 | (or excessively hard) to be achieved or fixed. |
| 114 | |
| 115 | **Confirmed** (`[query:keywords~=Confirmed Tickets]`:trac:) |
| 116 | For "Bugs", it indicates that a core developer was able to confirm the bug |
| 117 | in some way, validating the ticket. |
| 118 | For "New Features" and "Tasks", it indicates that the ticket has been |
| 119 | reviewed and its has been understood as a valid request. It's not there to |
| 120 | indicate our intentions on working on the ticket though. |
| 121 | |
| 122 | **HasPatch** (`[query:keywords~=HasPatch Tickets]`:trac:) |
| 123 | Tickets that contains a "valid" (checked by a core developer) proposal patch |
| 124 | attached to it. |
| 125 | A `[report:9 dedicated report]`:trac: has been created for it. |
| 126 | |
| 127 | **Discussion** (`[query:keywords~=Discussion Tickets]`:trac:) |
| 128 | Tickets that need more discussion to understand the expected behavior, its |
| 129 | correct interpretation, the correct way of handling then, etc... |
| 130 | |
| 131 | **Pending** (`[query:keywords~=Pending Tickets]`:trac:) |
| 132 | Marks tickets that need more information to be correctly understood or even |
| 133 | reproduced. |
| 134 | A `[report:10 dedicated report]`:trac: has been created to easily identify |
| 135 | expired tickets (pending for more than 30 days). |
| 136 | |
| 137 | **SF** (`[query:keywords~=SF Tickets]`:trac:) |
| 138 | Marks tickets that has been originally created at SourceForge and then |
| 139 | transfered to this site. |
| 140 | |
| 141 | **WorksForMe** (`[query:keywords~=WorksForMe Tickets]`:trac:) |
| 142 | Indicates that a core developer has tried to reproduce the problem with no |
| 143 | success, having the expected results instead. |
| 144 | ================ ============================================================================= |
| 145 | }}} |