15 | | Please provide the following when reporting new bugs. The more information you provide, the quicker the bug may be solved: |
16 | | * '''Descriptive summary''' - A "right to the point" phrase that best summarizes the issue that you are experiencing. |
17 | | * '''Steps to reproduce''' - This is the most important thing. We are not able to fix a bug if we cannot see it with our own eyes. A numbered list of actions to reproduce the issue is quite useful. |
18 | | * '''Browser and OS''' - Your computer configuration, OS, browser name and version. |
| 15 | Please provide the following when reporting new issues. The more information you provide, the quicker the problem may be solved: |
| 16 | * '''Descriptive summary''' - A "right to the point" phrase that best summarizes the issue that you are having. |
| 17 | * '''Steps to reproduce''' - This is the most important thing. We are not able to fix a bug if we cannot see it with our own eyes. A numbered list of actions to reproduce the issue is invaluable. |
| 18 | * '''Browser name and OS''' - Your computer configuration, OS, browser name and version. |
| 19 | * '''Editor configuration''' – Your editor version, integration method, editor build (you can attach your `build-config.js` file). If you are using a custom build or the problem only occurs in some specific editor packages, this information is crucial for us. |
20 | | * '''Sample data''' - For content-related bugs please attach a sample file with the text for testing. |
21 | | * '''Test case file''' - If possible, attach a Test Case file showing the bug. This is the best way to show us the problem that makes it quicker to solve it. |
22 | | * '''Build configuration''' - If you are using a custom build or the problem only occurs in some specific editor packages, attach the `build-config.js` file with your editor build configuration. |
| 21 | * '''Sample data''' - For content-related issues please attach a sample file from which we can get the text for testing. |
| 22 | * '''Test case file''' - If possible, attach a test case file showing the issue. This is the best way to show us the problem and make it quicker to solve. |
25 | | While filing the bug please bear these important things in mind: |
26 | | * '''Submit different reports for each bug'''. Do not include more than one bug in the same report. |
27 | | * The "Priority", "Milestone", and "Assign to" fields are reserved to the core development team. |
28 | | * '''Avoid using the "Keywords" field''' if you are not 100% sure on what to put there. |
| 25 | When filing an issue, please bear these important things in mind: |
| 26 | * '''Submit separate reports for each issue'''. Do not include more than one issue in the same report. |
| 27 | * The "Priority", "Milestone", and "Assign to" fields are reserved for the core development team. |
| 28 | * '''Avoid using the "Keywords" field''' if you are not 100% sure what to put there. |