The main Support workflow with Platform.sh is through support tickets. All issues regarding your projects should be reported by creating a support ticket through the console. They are triaged and addressed accordingly.
How to create a ticket
Support tickets with Platform.sh are created from Platform.sh Console, from the Support section.
- Go to Console
- From the User menu (top right) click on Support
- Click on New ticket
There are several fields that you need to fill in to help us troubleshoot the issue faster.
|Select a project from the list. Leave blank only if it is a general question, but if it is in any way related to a project (or group of projects), select a project from the list.
|Initial triage category - to help us triage your request to the appropriate team.
|Select the priority for your request. Make sure to select the priority that best describes your request/issue.
|Title of the ticket - a short statement of the request.
|A detailed description of the issue you are having, with steps on how to reproduce the issue, links to use, locations, etc.
|If you need to add attachments, you can do that too.
|Select the appropriate environment from the list that the issue applies to.
|URL we can use to reproduce the issue (see the symptoms you are describing).
To be able to provide support properly, all tickets must have correct priorities. During ticket triage, our team may raise or lower the ticket priority according to the guidelines below.
We are trying to make it as simple as possible, so there are 4 levels of urgency a request can have:
|Total failure or unavailability of your PRODUCTION SITE. Only PRODUCTION OUTAGE should be Urgent.
|Severe failures or high impact issues affecting a production site.
|Minor effect on production site or blocking development on non-production environments.
|Does not significantly impact a production site or the use of non-production environments
An issue may be Urgent if it affects production environments and meets these criteria with no possible workaround:
- results in downtime
- results in unacceptable load-times
- results in a loss of production data
- is a critical security update
- drastically reduces or prevents the ability of the development team to work on production
- prevents business-critical tasks from being completed
An issue affecting non-production environments that meets these criteria with no possible workaround may also be Urgent only if it prevents a launch from happening within 3 days of the planned launch date.
Ticket creation best practices
- Try finding the solution to the problem in Documentation or Help Center - self-service is the fastest service. If a solution is not found, proceed with the ticket creation...
- Be as detailed as possible when describing the issue.
- Provide basic information - project ID, environment, app/service.
- Provide detailed information about the problem - symptoms.
- Provide steps on how to reproduce the exact issue.
- Provide information on what you have tried so far.
- If it is a text (code blocks, error codes), copy-paste it, do not take screenshots of it.