This the support statement for Play SQL.
| Status |
| ||||||
|---|---|---|---|---|---|---|---|
| Date | From 14/10/2013 to 14/12/2013 (2 months) |
Please note:
- This is a young business. The SLA will be adjusted during the next few months, please keep a watch on the page.
- There are no penalties for non-respect of the SLA. Please refer to the license about this.
- The probation period will be monitored and results will be posted as a child page.
How to get Equally Legendary Support
Are you used to Atlassian's Legendary Support? I'll attempt to match it!
| Medium | Links |
|---|---|
| Web-based | Browse https://documentation.play-sql.com |
| Answers | Browse the "Play SQL" tag on Answers (or Ask on this tag) |
| By JIRA | https://playsql.atlassian.net, project Support |
| By email | playsql+public@gmail.com |
| By telephone | Production outage only, please request by email. |
Response times
| Level of severity | Description of severity | Response SLA | Standard Support | Enterprise Support |
|---|---|---|---|---|
| Level 1 | Add-on causing host application to malfunction, resulting in the majority of users unable to perform their normal functions. Please deactivate the add-on and let your users work. | 2 hours |
7.30 hrs x 5 days See Business Hours & Days | |
| Level 2 | Critical loss of add-on functionality resulting in high number of users unable to perform their normal functions. | 4 hours | ||
| Level 3 | Moderate loss of add-on functionality resulting in multiple users impacted in their normal functions. | 6 hours | ||
| Level 4 | Minor loss of add-on functionality or product feature question. | 8 hours | ||
Business hours
The support is operated from France. I recommend using http://www.worldtimebuddy.com/ for easy conversion.
| Shift | Times | Timezone |
|---|---|---|
| Morning | 9.30am-1pm | CET until 27th October 2013 (UTC +1) CEST until 30th March 2014 (UTC +2) |
| Afternoon | 2pm-6pm |
I often work in the evenings but I make no commitment in advance.
Business days
Work is from Monday to Friday. Days with degraded support will be written in this table at least one week in advance.
| Period | Normal Support | 6hrs support | No Support |
|---|---|---|---|
| Description | Support operating in normal mode | Level 1 and 2 will be answered within 6 hours | Support is provided in best effort mode. |
| Monday to Friday |  | ||
| 17th-21st October 2013 | | ||
| 22nd October 2013 | | ||
| 25th-29th October 2013 | | ||
| 1st November | Public Holiday | ||
| 11th November | Public Holiday | ||
| 23rd Dec - 3rd Jan 2014 | Christmas Holiday |
Definitions
- "Response" (as in "Response time"): A real human answers your request with currently available knowledge within SLA time. It doesn't mean the problem can be resolved at all. After answering to you, the real human can investigate the bug further and publish an upgrade, but this is not covered by the SLA.
- "Real human": Adrien Ragot in person.
...
| 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 |
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 |