Ticket Priority Levels Clause Samples

The Ticket Priority Levels clause defines how support or service requests are categorized based on their urgency or impact. Typically, it establishes several priority tiers—such as critical, high, medium, and low—each with corresponding response and resolution timeframes. For example, a critical issue might require immediate attention, while a low-priority request could be addressed within several days. This clause ensures that resources are allocated efficiently and that the most pressing issues are resolved first, thereby managing client expectations and improving service delivery.
Ticket Priority Levels. Priority levels are defined as: a) Priority 1 – P1 [Blocker] = Total disruption of service for majority of staff. Staff are unable to access the software or unable to perform significant business operations.
View SourceView Similar (11)
Ticket Priority Levels. Ticket priorities are assigned based on the technical importance of the problem related to the Customer’s implementation of DivvyCloud’s software. ● P1 = Licensed Software is completely inaccessible or the majority of its functionality is unusable. ● P2 = One or more key features of Licensed Software are unusable. ● P3 = Any other case where a Licensed Software feature is not operating as documented. ● P4 = Requests for changes in the way that Licensed Software works, or requests for new features in Licensed Software.
View Source
Ticket Priority Levels. Priority levels are defined as: a) Priority 1 (P1) [Blocker] = Total disruption of service for majority of staff. Staff are unable to access the software or are unable to perform significant business operations. b) Priority 2 (P2) [Critical] = Partial system outage effecting portion of the application and significant staff group. Significantly affecting functionality in critical areas such that no viable workaround is available. c) Priority 3 (P3) [Low] = Unable to perform some common business operation. Standard usage issue such that user functionality is disrupted, but a workaround is present. d) Priority 4 (P4) = System advice or enquiry. Low level issue not causing operational problem.
View Source

Related to Ticket Priority Levels

  • Senior Leverage Ratio The Borrower shall not permit its Senior Leverage Ratio at any time to exceed 2.75 to 1.00.

  • Secured Leverage Ratio Permit the Secured Leverage Ratio, as of the last day of any fiscal quarter of the Consolidated Group, to be greater than thirty-five percent (35%), or, for a period of four consecutive fiscal quarters following a Material Acquisition, forty percent (40%).

  • Staffing Levels To the extent legislative appropriations and PIN authorizations allow, safe staffing levels will be maintained in all institutions where employees have patient, client, inmate or student care responsibilities. In July of each year, the Secretary or Deputy Secretary of each agency will, upon request, meet with the Union, to hear the employees’ views regarding staffing levels. In August of each year, the Secretary or Deputy Secretary of Budget and Management will, upon request, meet with the Union to hear the employees’ views regarding the Governor’s budget request.

  • Collateral Requirements All amounts deposited or invested with financial institutions in excess of any insurance limit shall be collateralized in accordance with the Public Funds Investment Act, 30 ILCS 235/. The Superintendent or designee shall keep the Board informed of collateral agreements.

  • Consolidated Senior Leverage Ratio Permit the Consolidated Senior Total Leverage Ratio as of the end of each of the Fiscal Quarters ending on the dates set forth for the period of four Fiscal Quarters ending on such date below to be greater than the ratio set forth below opposite such period: March 31, 2008 through December 31, 2008 3.50 to 1.00 March 31, 2009 through December 31, 2009 3.25 to 1.00 March 31, 2010 through December 31, 2010 3.00 to 1.00 March 31, 2011 through December 31, 2011 2.50 to 1.00 March 31, 2012 through December 31, 2013 2.25 to 1.00