Ticket Details
A detailed a description of the issue goes a long way. Some useful information is the approximate time the issue occurred, the user's description of the issue, and any of your own observations.
There are two different types of URLs used when submitting tickets. Please be sure to include the one applicable to your ticket submission!
For tickets related to an issue a user has experienced, please include the project's share URL.
This allows us to jump directly into a user's project and see what went wrong. It is not possible for us to debug a user's project without a share URL, so please be sure to include it!
This URL can be found by clicking the share icon at the bottom left of the page and then selecting "Share".
Please be sure to include the writeable share URL! Otherwise, we only see a copy of the project, which doesn't include any of the learning materials (instructions, tasks, grades, etc.).
For tickets related to an issue with a content you are working on, please include the URL of that content, which can be found in your browser's navigation bar.
A picture says a thousand words, or so they say! Screenshots or screen recordings are very useful.
A screenshot and/or a copy paste of the project's JavaScript console output helps us identify any errors the user may have encountered in their project.
Below are some details on how to open the JavaScript console in common browsers!
Have the user right click and select the "Inspect" option
A window should appear within the web browser containing a navigation bar. Have the user select "Console"
Copy and paste the Console Output into a ticket
Have the user right click and select the "Inspect Element" option
A window should appear within the web browser containing a navigation bar. Have the user select "Console"
Copy and paste the Console output into a ticket
Screenshots of the console are also useful, if the output is not readily available.
