Redmine support by Easy team
The purpose of this on-going service is to back you up while using Easy Redmine. All our clients use the Basic Support Plan or can get higher level of service with the Priority Support plan. For specific support requirements, we can arrange individual support level and conditions.
Basic support plan
- Free of charge
- 24/7 support for cloud outage reports
- Support requests must be submitted through the client zone, or by email to firstname.lastname@example.org
- Tickets are prioritized according to the severity level (definition of severities is below)
- Response time is in our best effort; our team is committed to suggest a final solution within 24 business hours
- We use the rule of 3 replies on one ticket. If the issue is not solved, we will try calling the submitter for clarifications
Priority support plan
- Paid service
- 24/7 support for cloud outage reports
- Support requests may be submitted through the client zone, email or by phone to our international contact numbers and Skype
- Fast queue - tickets are handled with priority over basic support plan. Severities are still taken into consideration
- No ticket ping-pong - If the issue is not resolved by the first reply, we will try calling the submitter for additional information
- Our team is committed to resolve all tickets within the next business day
- We use various remote collaboration tools for a quicker resolution of your issues
Individual support plans
- Contact our sales team to find out more about individual support and SLAs
General information about support
Before submitting a ticket, please check our Knowledge base. Standard ticket submissions are via client zone and email. If you have paid priority support plan, you can also contact us by phone. When requesting support by phone, you will be asked for your contact information: name, company, direct phone, email. Without this information, we are not able to communicate the progress of your request.
To get the best response from our operators your report should contain technical data (production log, environment specifications, version of Easy Redmine, etc.), error messages and system information. Following the online submission with a phone call - referring to the ticket ID - can reduce response time as well as potential errors in the processing of information.
We recommend that you follow any Severity 1 and 2 online support ticket submissions with a phone call to Prague Development Centre.
Official support languages are English, French, German and Czech. If we receive tickets in another language, we use a web translator to understand the nature of the issue, but sometimes that is not enough. In case of other languages, we reply in English.
A bug report is accepted as legitimate, if:
- The application is hosted by Easy Software on cloud
- Installed on own server according to recommended procedures (http://www.easyredmine.com/installation) and with recommended configuration (https://www.easyredmine.com/documentation-of-easy-redmine/article/hardware-and-software-requirements-for-the-server-solution)
If the report is not validated in simulation tests, the bug may have been caused not by the application, but an external factor.
Easy Redmine Support Services uses the following definitions to classify issues:
Severity 1 (urgent)
A problem that severely impacts your use of the software in a production environment (such as loss of production data or complete malfunction of production system). The situation prevents you from using the software and there is no procedural workaround available.
Easy Cloud hotline* to report outages: +420 312 313 671
(*only cloud users, only unavailable applications, no user support)
Severity 2 (high)
A problem where the software is functioning but software's functions in a production environment are severely reduced. The situation has a high impact on parts of your business operations and there is no procedural workaround available.
Severity 3 (normal)
A problem that involves partial, non-critical loss of use of the software in a production environment. There is a medium-to-low impact on your business, but your business continues to function, with or without a procedural workaround.
Severity 4 (low)
A question regarding the general usage, reporting of a documentation error, or recommendation for a future product enhancement or modification. For production environments, there is a low-to-no impact on your business and the performance or functionality of your system. Your business continues to function, with or without a procedural workaround.
Every server configuration is specific, even if we provide the initial virtual machine with pre-installed application - it always must run on client's environment, which is beyond our control. That is why we have limited possibilities to provide support for incidents that are caused by the environment surrounding the application. We still expend our best effort to help you, regardless of the origin of the cause.
What is considered "server support"?
- Assistance with installation, upgrading or migrating data
- Assistance with deployment or launch of virtual machine
- Assistance with environment configuration (before, during, or after installation or deploy of the application)
- Assistance for services (such as cron jobs), components (such as disk), processes, web servers, application servers, database
- Assistance with email configuration
- Trainings for any of the above
- Investigation of local application failures
How is server support provided?
- Access to client's server for our technicians is an undeniable necessity
- The remote session is planned in advance for a specific time
- Postponement from client's side less than 24 hours before scheduled is sanctioned
- After each session, hours of the technician are billed
How are server support hours billed?
- Client prepays server support credit (minimum 1 man-day)
- After every session, hours spent by technicians are deducted from the credit
- Billable (deductible) hours are confirmed by client
- Spent and remaining hours are rounded to 10min
- If remaining credit is less than estimated time for a new session, client must "recharge" the credit before the session
- Server support credit is not a part of implementation or user support packages, it is billed separately
- Postponement of agreed date from client's side less than 24 hours before scheduled is sanctioned by 2 hours from the server support credit, even if no work was done!