...
Here are several points to keep in mind when filing a bug report. Providing these details will help us assess your issue's severity accurately and diagnose its cause more quickly.
Basic Information
- Please add an 'escape' label to the bug, to help us keep track of where our bug reports come from.
- Steps to reproduce the issue, if it is reproducible. There is a "Steps to Reproduce" field in the form if you edit an issue after creating it. But it is okay if you put this in the description. If you can provide steps to reproduce (meaning steps one can take to reproduce on a fresh test course), there's no need to provide any other information
- Please specify where you reproduced the bug. Was it on edx.org, edX Edge, or on your own installation? If it was on your own installation, are you running off of a named release (which one)? If you're running off of our master branch, an estimation of when you last updated your code base is very helpful.
- Expected vs. Actual behavior: how did the system behave? How did you expect it to behave in that situation?
- Business Value Statement: how is this bug impacting the value of our product?
- Screenshots, if that would illustrate the issue better.
- Your ticket's title should reflect the buggy behavior. Please do not include course-specific information in the title unless the bug is course-specific.
...