Support Priority Definitions

Priority 1 (Critical business impact)

Definition – Priority 1 selection indicates that customer is unable to use the CollabNet VersionOne application, resulting in a critical impact on business operations. This condition requires immediate resolution.

Priority 1 Condition – A Priority 1 issue has a crippling effect on customer’s business. i.e. production system is down.

Key Deliverables – Priority 1 service involves reacting to the customer’s emergency situation by immediately providing an appropriate resource. Unless another agreement is in place, Priority 1 issues will be serviced on a continual effort basis until the Priority 1 condition has been resolved. Resolution of Priority 1 conditions may include temporary relief, enabling the customer’s business to operate until a more comprehensive solution is provided. Priority 1 service delivery requires:

  • The product and the customer are eligible for customer support assistance
  • Customer is available 24x7 to actively collaborate with the analyst
  • System access or system information is available 24x7

Unless another agreement is in place, if the customer breaks continual effort, the situation will no longer be classified as critical, and will become lower priority. The case will then be serviced during normal business hours.

Response Objective – CollabNet VersionOne’s Support Program Policy (for CollabNet Products / for VersionOne Products) outlines how CollabNet VersionOne is organized to respond to all cases and application defects based on their assigned priorities.

Examples of Priority 1 case:

  • A production server has failed
  • Multiple users cannot access the production servers
  • Performance of the servers has degraded to an unusable level
  • Data is unrecoverable, corrupt, or lost

Examples of cases that are not typically classified as Priority 1:

  • Database is operational following a one–time outage; root cause analysis required
  • Feature Request or customization
  • Customer is not available for collaboration with support engineers after hours
  • First–time installation

NOTE: A Critical Situation does not automatically imply Priority 1. The problem’s associated business impact determines the priority.

Priority 2 (Significant business impact)

Definition – This indicates the CollabNet VersionOne application is usable but is severely limited.

Priority 2 Conditions

  • Issue is critical to customer’s business operations
  • Non–production system data with a valid support contract is inaccessible, cannot be archived or restored
  • Critical component returning error or not responding
  • Degraded application performance is having a serious negative impact on business
  • Root cause analysis is required on a previous Priority 1 issue  
  • A database or application error has occurred which severely impacts business operations

Key Deliverables – Priority 2 issues will be serviced as critical during normal business hours, unless an alternative customer agreement exists, and until the Priority 2 condition has been resolved. Rapid resolution should be provided using best effort. Priority 2 service delivery requires that:

  • Customer has an active CollabNet VersionOne support contract for the product in question
  • Customer is available during normal business hours

System access or system information is available during normal business hours.

Response Objective – CollabNet VersionOne’s Support Program Policy (for CollabNet Products / for VersionOne Products) outlines how CollabNet VersionOne is organized to respond to all cases and application defects based on their assigned priorities.

Priority 3 (Limited business impact)

Definition – This indicates the CollabNet VersionOne application is usable, but that some features (not critical to operations) are unavailable.

Priority 3 Conditions

  • Issue affects customer’s ability to meet near–term deadlines
  • Component returning error or not responding
  • Degraded performance is negatively impacting business operations
  • Acceptable workaround may exist
  • Issue is specific to one or a few users

Key Deliverables – Priority 3 issues are important for the customer and the customer’s services and will be serviced as such. These issues will be worked during normal business hours, until the Priority 3 condition has been resolved. Priority 3 service delivery requires that both the product and the customer are eligible for customer support assistance.

Response Objective – CollabNet VersionOne’s Support Program Policy (for CollabNet Products / for VersionOne Products) outlines how CollabNet VersionOne is organized to respond to all cases and application defects based on their assigned priorities.

Priority 4 (Minimal business impact)

Definition – This indicates the problem does not significantly impact operations, or that a reasonable workaround has been implemented.

Priority 4 Conditions

  • General question such as “how–to” or syntax questions
  • Issue with little or no impact
  • Documentation issues
  • Issue is essentially resolved but remains open for customer confirmation. Intermittent wait status with little or no customer interaction required

Key Deliverables – Priority 4 issues will be serviced as general issues during normal business hours until the Priority 4 condition has been resolved. Priority 4 service delivery requires that both the product and the customer are eligible for customer support assistance.

Response Objective – CollabNet VersionOne’s Support Program Policy (for CollabNet Products / for VersionOne Products) outlines how CollabNet VersionOne is organized to respond to all cases and application defects based on their assigned priorities.

Response Time Definitions

Priority Response Time
Critical - P1 1 hour - when logging a Critical Down ticket either via phone, voice mail, Support Portal, or email, an automatic notification is generated to the on-call Support Tech and the will respond within an hour.
Normal/Major - P2 8 business hours - If a ticket comes in during non-business hours, then the response time may be delayed. If a normal priority issue escalates into a critical issue, then please follow the instructions above to escalate the ticket to a Critical Down.
Minor - P3 24 business hours
Low - P4 5 days - You can usually expect a reply to a Low priority ticket within 1 business day, but circumstances may delay a reply up to a maximum of 5 days.

All tickets are different. We do not want to post an ETA on a resolution because who knows what the resolution will take before we actually dig into the ticket. Normally the support tech will let you know about how long a ticket might take to resolve, but that ETA is just a guess at an early stage. We might run into a bigger issue, assign a defect, or find bigger issues while troubleshooting the issue. If you want to know an ETA on ticket resolution, please discuss that with the support tech that is assigned to your ticket. If you wish to escalate the issue, please follow the procedures at the bottom of this page.