Project

General

Profile

Actions

Feature #8395

closed

Manage tickets for EGI.eu sites

Added by L'Orphelin Cyril over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
-
Start date:
10/30/2014
Due date:
% Done:

100%

Estimated time:
Story points-Velocity based estimate-Release3.1.1Release relationshipAuto

Description

Please add routing rule for ggus ticket creations:
For EGI.eu sites please use following SU mapping:
Site -> SU
GRIDOPS-MSG -> Messaging
GRIDOPS-OPSPORTAL -> Operations Portal
GRIDOPS-APEL -> APEL
GRIDOPS-ACCPORTAL ->Accounting Portal
GRIDOPS-METRICSPORTAL -> Metrics Portal
GRIDOPS-SAM -> ARGO/SAM EGI Support
GRIDOPS-MON -> ARGO/SAM EGI Support
GRIDOPS-SECTOOLS -> EGI Security Monitoring
GRIDOPS-GOCDB -> GOC DB
GRIDOPS-CATCHALL -> EGI Catch-all services
GRIDOPS-CTOOLS -> EGI.eu collaboration tools
GRIDOPS-UMDREPO -> EGI Software provisioning support
GRIDOPS-GGUS -> GGUS

Issue is that Egi.eu is not a typical NGI. Our "Sites" have own GGUS SU (as listed above).
This was raised some times ago that for EGI.eu "sites" tickets should be created not for NGI but for SU dedicated for "site".

Today I've created a ticket for "GRIDOPS-CATCHALL" site and in GGUS it was assigned to no one.
Some times ago I already raised this issue to you and I remember that it was implemented for a subset of Egi.eu "sites" but now we have in place all of them and I would like to cover all sites with the same rule.

Actions #1

Updated by L'Orphelin Cyril over 7 years ago

  • Release set to 3.1.1
Actions #3

Updated by L'Orphelin Cyril over 7 years ago

  • Status changed from New to Resolved
Actions #4

Updated by L'Orphelin Cyril over 7 years ago

  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF