I did not select level-xday option when creating a test ticket. When I
choose one and it works now.
I want to set different default level-xday value for each Queue. I goto
queue, edit "Queue2", select level-2days. But when creating ticket, the
default option value is still the value which
I followed your step to add the code, but it did not work.
1. I created custom field "SLA" and applied to queue "Queue2".
2. Update "Queue2" adding values to "SLA" these level option "level-1day",
"level-2days", "level-3days"
3. In file /opt/rt4/etc/RT_Siteconfig.d/RT_Siteconfig-duedate.pm,
I followed your step to add the code, but it did not work.
1. I created custom field "SLA" and applied to queue "Queue2".
2. Update "Queue2" adding values to "SLA" these level option "level-1day",
"level-2days", "level-3days"
3. In file /opt/rt4/etc/RT_Siteconfig.d/RT_Siteconfig-duedate.pm,
lLoss-SET2' => {
BusinessHours => 'SET TWO BH',
Resolve => { BusinessMinutes => 60*4 } },
'P1-Critical-TotalLoss-SET2' => {
Resolve => { RealMinutes => 60*2} },
);
Sally Ainsley | Lifecycle
Sally Ainsley wrote
> Hi
>
> We have managed this by setting up different SLAs for different queues.
>
> It was really fiddly and took lots of trial and error but we now have 5
> different sets of SLAS - we have default 1 and default 2 which apply to
> the
> majority of our Queues and then I
Emmanuel Lacour wrote
> Le 15/04/2016 04:11, Steven H a écrit :
>> I installed rt4.4.0
>>
>> When I configure queue, there is no place to input due dates. Instead
>> there
>> are fields "Starts" and "Due" which can be fill in a date such as
>> "2016-04-15 00:00:00". I did a test creating a
Yes, I'd like to have some examples, please.
--
View this message in context:
http://requesttracker.8502.n7.nabble.com/Due-dates-tp61729p61737.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.
-
RT 4.4 and RTIR Training Sessions
On 15-4-2016 10:15, Sally Ainsley wrote:
> Hi
>
> We have managed this by setting up different SLAs for different queues.
>
> It was really fiddly and took lots of trial and error but we now have 5
> different sets of SLAS - we have default 1 and default 2 which apply to the
> majority of our
Hi
We have managed this by setting up different SLAs for different queues.
It was really fiddly and took lots of trial and error but we now have 5
different sets of SLAS - we have default 1 and default 2 which apply to the
majority of our Queues and then I have 3 bespoke ones.
Each SLA set
Le 15/04/2016 04:11, Steven H a écrit :
> I installed rt4.4.0
>
> When I configure queue, there is no place to input due dates. Instead there
> are fields "Starts" and "Due" which can be fill in a date such as
> "2016-04-15 00:00:00". I did a test creating a ticket, the due date is what
> I set
We have an Urgency custom field in one of our queues, and I wrote a couple of
scrips to set the ticket due date and starting and ending priorities based on
that field's value. (One scrip fires on ticket creation, and one fires on a
change to the custom field's value.)
The scrip configuration
Hi Jose,
Check out the RT::SLA add on works great, and is easy to set up.
On Tue, Jan 19, 2010 at 8:54 PM, Jose de Paula Eufrasio Junior
jose.jun...@gmail.com wrote:
So, I want to use custom fields to classify the tickets on the support
queue as some pre-defined services. Each service has a
Hi Jose,
Damn laptop, clicked send before I was ready.
at any rate the SLA extension is per ticket, you can also have defaults
based on queue.
thanks,
Bill
On Tue, Jan 19, 2010 at 9:22 PM, William Graboyes
william.grabo...@theportalgrp.com wrote:
Hi Jose,
Check out the RT::SLA add on
13 matches
Mail list logo
