19 | | The following actions could be taken when confirming a ticket: |
20 | | |
21 | | * Resolve the ticket as "duplicate" if the ticket is determined to have the same cause as a ticket reported earlier. The "DUP of #XYZ" comment should be added, pointing to that ticket. |
22 | | |
23 | | * Mark the ticket with the "WorksForMe" keyword if the bug seems to not be present in the current trunk code. A comment should be added instructing the reporter to check it again and provide more information. A "WorksForMe" ticket expires in 30 days if no action is taken in the ticket, resolving it as "worksforme". |
24 | | |
25 | | * Resolve the ticket as "invalid" if it does not describe a problem with CKEditor. |
26 | | |
27 | | * Resolve the ticket as "wontfix" in the rare cases that the bug seems valid but there's a specific reason why it should not (or cannot) be fixed. If the reason is something we can't workaround, the "CantFix" keyword should be used. |
28 | | |
29 | | * Mark the ticket with the "Pending" keyword, if the ticket does not have enough information to move forward, asking the reporter for more details. A "Pending" ticket expires in 30 days if no action is taken in the ticket. |
30 | | |
31 | | * Mark the ticket with the "Confirmed" keyword. For browser specific tickets, the relative keyword should be appended: "IE", "IE6", "IE8", "Firefox", "Firefox2", "WebKit" and "Opera". |
32 | | |
33 | | * Mark the ticket with the "HasPatch" keyword, if a patch or descriptive code changes is provided, even if not analyzed and reviewed. |
| 21 | The following actions could be taken when confirming new ticket: |
| 22 | * Resolve the ticket as '''{{{duplicate}}}''' if the ticket is determined to have the same cause as a ticket reported earlier. The "DUP of #XYZ" comment should be added, pointing to that ticket. |
| 23 | * Resolve the ticket as '''{{{worksforme}}}''' if the bug seems to not be present in the current trunk code. A comment should be added instructing the reporter to check it again and provide more information. A ticket with this status, expires in 30 days if no action is taken in the ticket, resolving it as "worksforme". |
| 24 | * Resolve the ticket as '''{{{invalid}}}''' if it does not describe a problem with CKEditor. |
| 25 | * Resolve the ticket as '''{{{wontfix}}}''' in the rare cases that the bug seems valid but there's a specific reason why it should not (or cannot) be fixed. A comment with explanation of reasons, should be added. |
| 26 | * Check the option '''{{{request info}}}''' if the ticket does not have enough information to move forward, ticket would be returned to reporter, asking him for more details. Ticket status is set to ''pending'', and expires in 30 days if no action is taken. |
| 27 | * Check the option '''{{{confirmed}}}''' if the issue could be reproduced. For browser specific tickets, the relative keyword should be appended. List of allowed keywords could be found [http://dev.ckeditor.com/wiki/TicketSpecs here]. |
| 28 | * Mark the ticket with the '''{{{HasPatch}}}''' keyword, if a patch or descriptive code changes is provided, even if not analyzed and reviewed. |