This the support statement for Play SQL. Please note:
- I'll make everything I can to provide Equally Legendary Support, to match the one you have from Atlassian!
- Informational only: This SLA is an information of intent and does not engage Play SQL in any way. Please refer to the license for more information.
- As with any support, there is no guarantee that bugs can be fixed in a limited timeframe, that developments will be made specifically for you or that the root cause of your issue will be found. It is recommended to backup your database before performing administrative operations.
Equally Legendary Support
...
| Excerpt | ||||
|---|---|---|---|---|
| ||||
Find information about our support times and a direct link to our support. You can also read our SLA statement our Data Center escalation process. |
...
Support
The best way to contact us is the Service Desk portal.
Medium | Links |
|---|---|
Documentation |
...
Technical documentation |
...
...
support@requirementyogi.atlassian.net (Not recommended, please create a ticket instead) | |
Issue trackers |
...
...
High Uptime
It is important you have autonomy to solve your problems. Therefore, we have
the Documentation website (Http and Https), the JIRA issue tracker,
the Marketplace and the Sandbox
monitored by an independent provider, Uptime Robot.
With a 5-minutes probe interval, we reach close to 100% availability.
Last unavailability: Regular upgrade of our JIRA OnDemand instance
by Atlassian (9 minutes).
This screenshot is an archived copy of our monitoring tool.
Business hours
Play SQL is located in France. Germany and UK have the best support response. I recommend using http://www.worldtimebuddy.com/ for easy conversion.
| Timezone | Most responsive support | Dinner time | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| France (Play SQL) | 8 | 9 | 10:00 | 11:00 | 12:00 | 13:00 | 14:00 | 15:00 | 16:00 | 17:00 | 18:00 | 19 | 20 | 21 | 22 | 23 | 0:00 | 1am+ |
| San Francisco, USA | 11pm | 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am | 12pm | 1pm | 2pm | 3pm | 4pm+ |
| Sydney, Australia | 6pm | 7pm | 8pm | 9pm | 10pm | 11pm | 12am | 1am | 2am | 3am | 4am | 5am | 6am | 7am | 8am | 9am | 10am | 11am+ |
Temporary leave notice
- Reduced times from to
- Unavailable from to
...
Response times
Type | |
|---|---|
4hrs (1/2 day) | Cloud apps with Blocking priority, Data Center apps with Blocking and High priority. |
8hrs (1 working day) | Cloud apps with Priority High and Medium priority, Data Center apps with Low priority. |
3 days | Data Center and Cloud apps with Low priority or without priority. |
Our public target is to provide an answer within the above times:
During working days 10am-6pm European time (8hrs means 1 working day),
Except on French bank holidays and temporary leave.
This SLA is an information of intent, and does not engage Requirement Yogi in any way.
Bugfixes and improvements are explicitly not part of any SLA, as software complexity makes it difficult to estimate the timeframe.
Data Center escalation process
Data Center customers operate our products in mission critical environments and want to feel confident that if issues arise they can be addressed quickly. We want to reassure them that we'll monitor the response times to their support requests:
Step 1 | Create a support request on https://support.requirementyogi.com. Don't forget to mention "Data Center" to be in the right queue.  | We actively monitor the response times on this queue. Response times are explicited above. |
|---|---|---|
Step 2 | Please wait. We have received your request and we will answer. | If we do not answer within the due timeframe, proceed to the next section. |
Step 3 | Please do not escalate when you are not meeting a blocking issue which have received no answer. In the support request, click "Escalate".  | We will receive an email on our mobile phones, telling us you Our target on escalation is to provide an answer within 4hrs during working days. |
Step 4 | Contact the manager using the email address received in the |