The "REQUIRED INFO" section is, you guessed it, required. Your bug report will not be evaluated unless all items in that section are provided. All other info is optional, but any details you can provide will speed up the process and make it much more likely that your bug report will get looked into quickly.
A reproducible test case, if possible, is the best thing you can provide. An ideal test case would be a self-contained block of code that could be dropped directly into an existing test page under the Extensible examples folder. Another good option would be a link to JS Fiddle that demonstrates the issue.
Copy and paste the following template into your new bug report, then edit as needed:
- Code: Select all
[b]General description of problem:[/b]
[b]Timezone and locale (if applicable):[/b]
[b]Extensible version(s) tested:[/b]
[b]Ext JS version(s) tested:[/b]
[b]OS + Browser name/version(s) tested:[/b]
[b]Detailed steps to reproduce:[/b]
[*]step 1 ...
[*]step 2 ...[/list]
[b][u][color=#008000]OTHER HELPFUL INFO[/color][/u][/b]
[code]A self-contained code snippet that reproduces the issue[/code]
[b]Live URL to test case:[/b]
[code]Your proposed fix or workaround[/code]
[b]Screenshots or video links:[/b]
[b]Research or debugging notes:[/b]