The original plan for Notify was that an email was sent to the site
alerting them of the ticket in case they were awake when the TPMs and
ROC weren't. I think this has been modified to automatically assign the
ticket to the relevant ROC who most likely then assign to the site.
> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Stephen Burke
> Sent: 22 January 2010 10:42
> To: [log in to unmask]
> Subject: Re: Help GGUS
>
> Testbed Support for GridPP member institutes
> > [mailto:[log in to unmask]] On Behalf Of John Gordon said:
> > I'm on a mission to cut out unnecessary message looping in GGUS. I
am
> > sure you have all seen cases where you have submitted a ticket about
> a
> > problem on your own site and it has been assigned back to you.
>
> One component of that is a result of the move to direct submission of
> tickets to sites. I've seen quite a few tickets where admins select
> their own site in "Notify site" without realising that if they do that
> it assigns the ticket to that site! I've pointed that out a few times
> to
> the GGUS developers and there is now a popup help message which
> explains
> it, but I suspect that most people don't read it - I think it still
> isn't clear in the submission form itself (to me "notify" is not the
> same as "assign").
>
> For TPM-assigned tickets it should in theory be better with the new
> TPM model where there will be a small number of dedicated TPMs on
> frequent rotation.
>
> Stephen
> --
> Scanned by iCritical.
--
Scanned by iCritical.
|