Best Practices for Submitting Support Tickets

To help us address your concerns quickly and effectively, please follow these best practices when submitting a support ticket:

1. Be as Descriptive as Possible

• Clearly explain the issue or request you're experiencing
• Include steps to reproduce the problem, if applicable
• Mention any error messages you've encountered
• Specify which part of the curriculum or which book you're working with

2. Share Images or Screenshots

• Visual information can greatly assist in understanding the issue
• Include screenshots of error messages or unexpected behavior
• If sharing code, consider using a screenshot to preserve formatting

3. Provide Relevant Links

• Link to the specific GitHub URL for the page where you're encountering an issue
• If referring to a particular lesson or exercise, include a direct link

4. Choose the Appropriate Ticket Type and Category

• Select the correct ticket type (Issue, Feature Request, or Idea)
  • View our article that provides more information on ticket types: Understanding Ticket Types
• Choose the most relevant category (JavaScript, Java, C#, Data Analysis, Liftoff, or GitHub)

5. Suggest a Change (if applicable)

• If you have an idea for how to resolve the issue or implement a feature, share it
• Your perspective as a learner is valuable to us

6. Use a Clear Subject Line

• Summarize the main point of your ticket in the subject line
• This helps our team quickly understand the nature of your request

By following these best practices, you'll help us provide faster and more accurate support. Thank you for contributing to the improvement of our programs!