SLA guidelines
» Issues
Priority | Description | Response Time | Resolution Time (Best effort) |
---|---|---|---|
Blocker/ Critical | Fundamentally broken, impact on the entire application. No workaround options available. Examples: ◦ Wrong data being displayed ◦ Cannot write / writingwrong values ◦ Existing view/ dashboard / wizard does not load ◦ Cannot login ◦ Valid MDX / rest calls are failing against the server ◦ Security issue – data leak, critical vulnerability ◦ Broken functionality across the application (export excel / PDF / Import data) | 24 hours
| Addressed through a Fix Pack ASAP Gets addressed on the current week / sprint |
Major | Major functionality partially broken, impact on a specific report. Examples:
| 24 hours
| Addressed through a Fix Pack Gets addressed on the upcoming 2 week / sprints |
Minor | Small impact on the application, does not have impact on end users. Examples:
| 24 hours
| Addressed through a regular release cycle Goal to include a fix in 1 or 2 releases |
Info |
---|
General comment about performance issues: Needs to be proved that they are caused by UX and not by e.g. TM1 server, infrastructure or network issues. |
» Enhancements
Priority | Response Time |
---|---|
Only | 7 days
|