Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "FAQ GGUS-Priority-Colour"

From EGIWiki
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{GGUS-header|GGUS-Priority-Colour}}  
{{GGUS-header|GGUS-Priority-Colour}}  


== What is the purpose of the priority colours in GGUS? ==
== What is the purpose of the priority colours in GGUS? ==
The priority colours in GGUS should help supporters getting an overview of the most important tickets.
It is different to the algorithm used in the GGUS [https://ggus.eu/pages/metrics/download_escalation_reports.php escalation reports].
The priority colours have no impact on the metrics generated with the GGUS report generator or manually by the GGUS team.


== Which colours are used? ==
The priority colours in GGUS should help supporters getting an overview of the most important tickets. The priority colours have no impact on the metrics generated with the GGUS report generator or manually by the GGUS team.  
Currently the following colours are used for open states:
* green,
* yellow,
* amber and
* red.
For terminal states GGUS uses
* light blue for status “unsolved” and
* blue for status “solved” and “verified”.


== Which fields are affecting the priority colour algorithm? ==
== Which colours are used? ==
The priority colour algorithm is affected by the status value and the priority of a ticket.
The priority colour calculation for tickets in status "assigned" is based on different values than for tickets in any other open status.


== Are office hours and weekends considered in the priority colour algorithm? ==
Currently the following colours are used for open states:  
Office hours and weekends are taken into consideration when calculating the priority colour . The system assumes usual office hours from 07:00 to 15:00 o’clock UTC from Monday to Friday for all support units. Different time zones are considered as far as possible.


== Is the priority colour calculated different for the various status values? ==
*green,
The priority colour calculation starts after a ticket gets assigned to any support unit. The support units should change the ticket status to "in progress" or any other open status after receiving the ticket. Thus the support unit has responded to the ticket ('''response time'''). After such a status change the priority is reset to "green" and the calculation of the priority colour starts again from scratch.
*yellow,
*amber and
*red.
 
For terminal states GGUS uses
 
*light blue for status “unsolved” and
*blue for status “solved” and “verified”.
 
== Which fields are affecting the priority colour algorithm?  ==
 
The priority colour algorithm is affected by the status value and the priority of a ticket. The priority colour calculation for tickets in status "assigned" is based on different values than for tickets in any other open status.
 
== Are office hours and weekends considered in the priority colour algorithm?  ==
 
Office hours and weekends are taken into consideration when calculating the priority colour . The system assumes usual office hours from 07:00 to 15:00 o’clock UTC from Monday to Friday for all support units. Different time zones are considered as far as possible.
 
== Is the priority colour calculated different for the various status values? ==
 
The priority colour calculation starts after a ticket gets assigned to any support unit. The support units should change the ticket status to "in progress" or any other open status after receiving the ticket. Thus the support unit has responded to the ticket ('''response time'''). After such a status change the priority is reset to "green" and the calculation of the priority colour starts again from scratch.
 
== What is the algorithm for middleware related tickets?  ==
 
The priority colour for tickets dealing with middleware related problems is calculated according to the [[FAQ GGUS-PT-QoS-Levels|Quality of Support]] the PTs voted for. The priority colour changes after a dedicated amount of working hours as listed in the table below. The priority colour calculation is processed every 15 minutes.  


== What is the algorithm for middleware related tickets? ==
The priority colour for tickets dealing with middleware related problems is calculated according to the [[FAQ_GGUS-PT-QoS-Levels | quality of service]] the PTs voted for.
The priority colour changes after a dedicated amount of working hours as listed in the table below. The priority colour calculation is processed every 15 minutes.
{| cellspacing="0" cellpadding="2" border="1"
{| cellspacing="0" cellpadding="2" border="1"
|-
|-
! scope="col" | Level of service
! scope="col" | QoS Level  
! scope="col" | Ticket priority
! scope="col" | Ticket priority  
! scope="col" | Colour
! scope="col" | Colour  
! scope="col" | Working hours
! scope="col" | Working hours  
! scope="col" | Colour
! scope="col" | Colour  
! scope="col" | Working hours
! scope="col" | Working hours  
! scope="col" | Colour
! scope="col" | Colour  
! scope="col" | Working hours
! scope="col" | Working hours
|-
|-
| Base
| Base  
| less urgent
| less urgent  
| Yellow
| Yellow  
| 20
| 20  
| Amber
| Amber  
| 30
| 30  
| Red
| Red  
| 40
| 40
|-
|-
|  
|  
| urgent
| urgent  
|  
|  
| 20
| 20  
|  
|  
| 30
| 30  
|  
|  
| 40
| 40
|-
|-
|  
|  
| very urgent
| very urgent  
|  
|  
| 20
| 20  
|  
|  
| 30
| 30  
|  
|  
| 40
| 40
|-
|-
|  
|  
| top priority
| top priority  
|  
|  
| 20
| 20  
|  
|  
| 30
| 30  
|  
|  
| 40
| 40
|-
|-
| Medium
| Medium  
| less urgent
| less urgent  
| Yellow
| Yellow  
| 20
| 20  
| Amber
| Amber  
| 30
| 30  
| Red
| Red  
| 40
| 40
|-
|-
|  
|  
| urgent
| urgent  
|  
|  
| 20
| 20  
|  
|  
| 30
| 30  
|  
|  
| 40
| 40
|-
|-
|  
|  
| very urgent
| very urgent  
|  
|  
| 4
| 4  
|  
|  
| 6
| 6  
|  
|  
| 8
| 8
|-
|-
|  
|  
| top priority
| top priority  
|  
|  
| 4
| 4  
|  
|  
| 6
| 6  
|  
|  
| 8
| 8
|-
|-
| Advanced
| Advanced  
| less urgent
| less urgent  
| Yellow
| Yellow  
| 20
| 20  
| Amber
| Amber  
| 30
| 30  
| Red
| Red  
| 40
| 40
|-
|-
|  
|  
| urgent
| urgent  
|  
|  
| 4
| 4  
|  
|  
| 6
| 6  
|  
|  
| 8
| 8
|-
|-
|  
|  
| very urgent
| very urgent  
|  
|  
| 4
| 4  
|  
|  
| 6
| 6  
|  
|  
| 8
| 8
|-
|-
|  
|  
| top priority
| top priority  
|  
|  
| 2
| 2  
|  
|  
| 3
| 3  
|  
|  
| 4
| 4
|}
|}
== What is the algorithm for tickets other than middleware? ==
 
The priority colour for other tickets is calculated according to the values inherited from EGEE era.
== What is the algorithm for tickets other than middleware? ==
The priority colour changes after a dedicated amount of working hours as listed in the table below. The priority colour calculation is running every 15 minutes.
 
The priority colour changes after a dedicated amount of working hours as listed in the table below. The priority colour calculation is running every 15 minutes.  


{| cellspacing="0" cellpadding="2" border="1"
{| cellspacing="0" cellpadding="2" border="1"
|-
|-
! scope="col" | Ticket priority
! scope="col" | Ticket priority  
! scope="col" | Colour
! scope="col" | Colour  
! scope="col" | Working hours
! scope="col" | Working hours
|-
|-
| less urgent
| less urgent  
| Yellow
| Yellow  
| 20
| 20
|-
|-
|  
|  
| Amber
| Amber  
| 30
| 30
|-
|-
|  
|  
| Red
| Red  
| 40
| 40
|-
|-
| urgent
| urgent  
| Yellow
| Yellow  
| 20
| 20
|-
|-
|  
|  
| Amber
| Amber  
| 30
| 30
|-
|-
|  
|  
| Red
| Red  
| 40
| 40
|-
|-
| very urgent
| very urgent  
| Yellow
| Yellow  
| 16
| 16
|-
|-
|  
|  
| Amber
| Amber  
| 24
| 24
|-
|-
|  
|  
| Red
| Red  
| 32
| 32
|-
|-
| top priority
| top priority  
| Yellow
| Yellow  
| 12
| 12
|-
|-
|  
|  
| Amber
| Amber  
| 18
| 18
|-
|-
|  
|  
| Red
| Red  
| 24
| 24
|}
|}


== What if I have questions which are not dealt with by this FAQ?  ==
== What if I have questions which are not dealt with by this FAQ?  ==
Please send your question by mail to ''supportatnospamggus.org'' or submit a GGUS ticket.
Please send your question by mail to ''supportatnospamggus.org'' or submit a GGUS ticket.

Latest revision as of 08:48, 14 August 2014

GGUS-logo.jpg


GGUS wiki / GGUS Documentation


GGUS-Priority-Colour



What is the purpose of the priority colours in GGUS?

The priority colours in GGUS should help supporters getting an overview of the most important tickets. The priority colours have no impact on the metrics generated with the GGUS report generator or manually by the GGUS team.

Which colours are used?

Currently the following colours are used for open states:

  • green,
  • yellow,
  • amber and
  • red.

For terminal states GGUS uses

  • light blue for status “unsolved” and
  • blue for status “solved” and “verified”.

Which fields are affecting the priority colour algorithm?

The priority colour algorithm is affected by the status value and the priority of a ticket. The priority colour calculation for tickets in status "assigned" is based on different values than for tickets in any other open status.

Are office hours and weekends considered in the priority colour algorithm?

Office hours and weekends are taken into consideration when calculating the priority colour . The system assumes usual office hours from 07:00 to 15:00 o’clock UTC from Monday to Friday for all support units. Different time zones are considered as far as possible.

Is the priority colour calculated different for the various status values?

The priority colour calculation starts after a ticket gets assigned to any support unit. The support units should change the ticket status to "in progress" or any other open status after receiving the ticket. Thus the support unit has responded to the ticket (response time). After such a status change the priority is reset to "green" and the calculation of the priority colour starts again from scratch.

What is the algorithm for middleware related tickets?

The priority colour for tickets dealing with middleware related problems is calculated according to the Quality of Support the PTs voted for. The priority colour changes after a dedicated amount of working hours as listed in the table below. The priority colour calculation is processed every 15 minutes.

QoS Level Ticket priority Colour Working hours Colour Working hours Colour Working hours
Base less urgent Yellow 20 Amber 30 Red 40
urgent 20 30 40
very urgent 20 30 40
top priority 20 30 40
Medium less urgent Yellow 20 Amber 30 Red 40
urgent 20 30 40
very urgent 4 6 8
top priority 4 6 8
Advanced less urgent Yellow 20 Amber 30 Red 40
urgent 4 6 8
very urgent 4 6 8
top priority 2 3 4

What is the algorithm for tickets other than middleware?

The priority colour changes after a dedicated amount of working hours as listed in the table below. The priority colour calculation is running every 15 minutes.

Ticket priority Colour Working hours
less urgent Yellow 20
Amber 30
Red 40
urgent Yellow 20
Amber 30
Red 40
very urgent Yellow 16
Amber 24
Red 32
top priority Yellow 12
Amber 18
Red 24

What if I have questions which are not dealt with by this FAQ?

Please send your question by mail to supportatnospamggus.org or submit a GGUS ticket.