Bug Reporting Guidelines

Summary:

Provide what happened, what you were doing when it happened, and why you think it's a problem. If you receive an error message, provide the content of the error message (or an approximation of it). Provide specifics and refrain from using vague language or colloquialisms. Instead of using descriptive words or phrases when something "looks bad," "has issues," "is odd," "is wrong," "is acting up," or "is failing," be concise and describe how something is looking or acting, why you believe there is a problem, and provide any error messages that will support the problem being reported.

Steps to Reproduce:

Describe the step-by-step process to reproduce the bug. Note: It is better to include too much information than not enough, as this minimizes the amount of back-and-forth communications. Note: Be very specific and be sure to provide details, opposed to high-level actions.

Expected Results:

Describe what you expected to happen when executing the steps to reproduce.

Actual Results:

Explain what actually occurred.

Workaround:

If you have found a workaround for this problem, describe it.