efine as a new group
> and it may be this setting that makes the time carry on rather than start
> from beginning again)
>
> o Reset Goal for Same Request? = Yes
>
> o Allow Service Target to Re-Open? = No
>
>
>
> Regards
>
> Jiri
>
>
>
> *F
: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Mike Buck
Sent: 20 May 2010 15:17
To: arslist@ARSLIST.ORG
Subject: Re: ITSM7.5 Incident SLAs
**
Thank you Jiri, I really appreciate the time you took to respond.
I actually tried something very similar to what you
; Remedy Specialist
>
> LCH.Clearnet <http://www.lchclearnet.com/>
>
>
>
>
>
>
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arsl...@arslist.org] *On Behalf Of *Mike Buck
> *Sent:* 20 May 2010 14:30
> *To:* arslist@ARSLIST.ORG
&
st
LCH.Clearnet<http://www.lchclearnet.com/>
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Mike Buck
Sent: 20 May 2010 14:30
To: arslist@ARSLIST.ORG
Subject: ITSM7.5 Incident SLAs
**
Hi
Does anyone know how to configure things so that the
Hi
Does anyone know how to configure things so that the SLA re-attaches when
it's re-assigned to another group? The new group's business hours (new
group's Business Entity) should be used in calculating the new SLA Due Date.
Currently Response and Resolution SLAs get attached to Incidents using
5 matches
Mail list logo