To enable us to quickly process, reproduce and fix bugs we have a simple format that we ask you to use when reporting any issues. Below is a template you can copy and paste when you create your bug thread and simply fill in the blanks.

The items in the first section - exact Ext JS version, browser, description and a test case - are all required before we can enter the bug for correction. Any additional information you can give in the second section will generally help us fix the bug faster.

The next post in this thread uses the code below to show an example of what a good bug report looks like:

Code:
[U][B][COLOR="green"]REQUIRED INFORMATION[/COLOR][/B][/U]


[B][U]Ext version tested:[/U][/B]
[LIST][*]Ext 4.____ rev ____[/LIST]

[B][U]Browser versions tested against:[/U][/B]
[LIST][*]____[*]IE8[*]FF3 (firebug 1.3.0.10 installed)[*]Safari 4[/LIST]

[B][U]DOCTYPE tested against:[/U][/B]
[LIST][*]____[/LIST]

[B][U]Description:[/U][/B]
[LIST][*]Describe the problem in greater detail here, summarizing the behavior.[/LIST]

[B][U]Steps to reproduce the problem:[/U][/B]
[LIST][*] foo[*] bar[/LIST]

[B][U]The result that was expected:[/U][/B]
[LIST][*] foo[*] bar[/LIST]

[B][U]The result that occurs instead:[/U][/B]
[LIST][*] foo[*] bar[/LIST]

[B][U]Test Case:[/U][/B]

[CODE]
    <<insert working code to reproduce the report >>
[/CODE]



[U][B][COLOR="green"]HELPFUL INFORMATION[/COLOR][/B][/U]


[B][U]Screenshot or Video:[/U][/B]
[LIST][*]attached[/LIST]

[B]See this URL for live test case:[/B] http://


[B][U]Debugging already done:[/U][/B]
[LIST][*]none[/LIST]

[B][U]Possible fix:[/U][/B]
[LIST][*]not provided[/LIST]

[B][U]Additional CSS used:[/U][/B]
[LIST][*]only default ext-all.css[*]custom css (include details)[/LIST]

[B][U]Operating System:[/U][/B]
[LIST][*]________[*]WinXP Pro[/LIST]