This version of GitHub Enterprise will be discontinued on 2022-02-16. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Creating a support ticket

You can use the GitHub Support portal to create a support ticket and speak to GitHub Support.

About support tickets

If you have previously contacted GitHub Enterprise Support through the deprecated GitHub Enterprise Support portal, you should use the GitHub Support portal to open new tickets but you can still view your past tickets at https://enterprise.githubsupport.com.

To open, view, and comment on support tickets associated with an enterprise account or organization owned by an enterprise account, you must have support entitlements for the account. Enterprise owners and billing managers automatically have a support entitlement, and enterprise owners can add support entitlements to enterprise members. For more information, see "Managing support entitlements for your enterprise."

You can create your ticket using the GitHub Support portal or, if you would like to include diagnostics with your support ticket, you can use the GitHub Enterprise Server Management Console.

After you create your ticket, you can view your ticket and the responses from GitHub Support on the GitHub Support portal. For more information, see "Viewing and updating support tickets."

What to include in your support ticket

Providing GitHub Support with everything they need to understand, locate, and reproduce an issue will allow for a faster resolution and less back-and-forth between yourself and the support team. To ensure GitHub Support can assist you, consider the following points when you write your ticket:

  • Obtain information that can help GitHub Support track, prioritize, reproduce, or investigate the issue.
  • Include full URLs, repository names, and usernames wherever possible.
  • Reproduce the issue if applicable and be prepared to share the steps.
  • Be prepared to provide a full description of the issue and expected results.
  • Copy exact wording of all error messages related to your issue.
  • Determine if there is an existing ticket number in any ongoing communications with GitHub Support.
  • Include relevant logs and attach any screenshots that demonstrate the issue.

Choosing a contact person

Especially for tickets with Urgent priority, the person contacting GitHub Support should:

  • Be knowledgeable in your internal systems, tools, policies, and practices.
  • Be a proficient user of GitHub Enterprise Server.
  • Have full access and permissions to any services that are required to troubleshoot the issue.
  • Be authorized to make the recommended changes to your network and any applicable products.

Creating a support ticket using the support portal

  1. Navigate to the GitHub Support portal.
  2. Select the Account or organization dropdown menu and click the name of the account your support ticket is regarding. Screenshot of the "Account or organization" dropdown menu.
  3. Select the From drop-down menu and click the email address you'd like GitHub Support to contact. Screenshot of the "From" dropdown menu.
  4. Select the Product dropdown menu and click GitHub Enterprise Server (self-hosted). Screenshot of the "Product" dropdown menu.
  5. If prompted, select the Server installation dropdown menu and click the installation your support ticket is regarding. If the installation is not listed, click Other. Screenshot of the "Server Installation" dropdown menu
  6. Select the Release series dropdown menu and click the release your GitHub Enterprise Server instance is running. Screenshot of the "Release series" dropdown menu
  7. Select the Priority dropdown menu and click the appropriate urgency. For more information, see "About ticket priority." Screenshot of the "Priority" dropdown menu.
    • Choose Urgent to report fatal system failures, outages impacting critical system operations, security incidents, and expired licenses.
    • Choose High to report issues impacting business operations, including system performance issues, or to report critical bugs.
    • Choose Normal to make technical requests like configuration changes and third-party integrations, and to report non-critical bugs.
    • Choose Low to ask general questions and submit requests for new features, purchases, training, or health checks.
  8. Optionally, if your account includes GitHub Premium Support and your ticket is urgent or high priority, you can request a callback in English. Select Request a callback from GitHub Support, select the country code dropdown menu to choose your country, and enter your phone number. Screenshot of the "Request callback" checkbox, "Country code" dropdown menu, and "Phone number" text box.
  9. Under "Subject", type a descriptive title for the issue you're having. Screenshot of the "Subject" text box.
  10. Under "How can we help", provide any additional information that will help the Support team troubleshoot the problem. You can use markdown to format your message. Screenshot of the "How can we help" text area. Helpful information may include:
    • Steps to reproduce the issue
    • Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency)
    • Exact wording of error messages
  11. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard.
  12. Click Send request. Screenshot of the "Send request" button.

Creating a ticket using the GitHub Enterprise Server Management Console

  1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .

    Screenshot of the rocket ship icon for accessing site admin settings

  2. If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.

    Screenshot of "Site admin" link

  3. In the left sidebar, click Management Console. Management Console tab in the left sidebar

  4. If prompted, type your Management Console password. Management Console unlock screen

  5. In the upper right of the Management Console, click Support. Button to access Support area

  6. If you'd like to include diagnostics with your support ticket, Under "Diagnostics", click Download diagnostic info and save the file locally. You'll attach this file to your support ticket later. Screenshot of button labelled "Download diagnostics info" on Management Console Support page.

  7. To complete your ticket and display the GitHub Support portal, under "Open Support Request", click New support request. Screenshot of button labelled "New support request" on Management Console Support page.

  8. Select the Account or organization dropdown menu and click the name of the account your support ticket is regarding. Screenshot of the "Account or organization" dropdown menu.

  9. Select the From drop-down menu and click the email address you'd like GitHub Support to contact. Screenshot of the "From" dropdown menu.

  10. Select the Product dropdown menu and click GitHub Enterprise Server (self-hosted). Screenshot of the "Product" dropdown menu.

  11. If prompted, select the Server installation dropdown menu and click the installation your support ticket is regarding. If the installation is not listed, click Other. Screenshot of the "Server Installation" dropdown menu

  12. Select the Release series dropdown menu and click the release your GitHub Enterprise Server instance is running. Screenshot of the "Release series" dropdown menu

  13. Select the Priority dropdown menu and click the appropriate urgency. For more information, see "About ticket priority." Screenshot of the "Priority" dropdown menu.

    • Choose Urgent to report fatal system failures, outages impacting critical system operations, security incidents, and expired licenses.
    • Choose High to report issues impacting business operations, including system performance issues, or to report critical bugs.
    • Choose Normal to make technical requests like configuration changes and third-party integrations, and to report non-critical bugs.
    • Choose Low to ask general questions and submit requests for new features, purchases, training, or health checks.
  14. Optionally, if your account includes GitHub Premium Support and your ticket is urgent or high priority, you can request a callback in English. Select Request a callback from GitHub Support, select the country code dropdown menu to choose your country, and enter your phone number. Screenshot of the "Request callback" checkbox, "Country code" dropdown menu, and "Phone number" text box.

  15. Under "Subject", type a descriptive title for the issue you're having. Screenshot of the "Subject" text box.

  16. Under "How can we help", provide any additional information that will help the Support team troubleshoot the problem. You can use markdown to format your message. Screenshot of the "How can we help" text area. Helpful information may include:

    • Steps to reproduce the issue
    • Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency)
    • Exact wording of error messages
  17. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard.

  18. Click Send request. Screenshot of the "Send request" button.

Further reading

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.