[rt-users] error "could not find component" - upgrading to 4.4.0

Hi, We are upgrading from 4.2.9 to 4.4.0 The error in the attached image results when attempting to upgrade a ticket, url: http://ticket/Ticket/Update.html?Action=Respond=rejected=833 Remarks: 1.- A file with the same name exists in another location: $ find . -name 'ShowSimplifiedRecipients'

Re: [rt-users] SLA Extension change SLA on queue change

Sally, Tried this with unique alpha names for the SLA’s in between two queues. Still no such luck. Any other ideas? Thank you! Nick > On Jun 27, 2016, at 11:25 AM, Sally Ainsley > wrote: > > Maybe the default only works when the SLA is blank in which

Re: [rt-users] SLA Extension change SLA on queue change

Hi Nick Can you use a "default" SLA for each queue - then in theory when the ticket changed queue the SLA would update to be the default? Not sure it would work but we have default SLAs for our queues as well as ones that are chosen by users. (ie default is used the user/requestor leaves blank.

Re: [rt-users] SLA Extension change SLA on queue change

Hi Sally, Thanks for the reply. I believe I have the default SLA set but it does not apply when the queue is changed. But I’m going to double check my defaults just in case I am mistaken. Thank you! Nick > On Jun 27, 2016, at 11:22 AM, Sally Ainsley >

Re: [rt-users] Re-Display Ticket with added warning if owner changed during responding

On 6/27/16 3:25 AM, David Schmidt wrote: On 24.06.2016 14:19, Jim Brandt wrote: On 6/23/16 8:19 AM, David Schmidt wrote: Hello In case someone takes the ticket ownership wile I am composing a response I would like to redisplay the ticket (the submitted response shouldnt be deleted) and add a

[rt-users] SLA Extension change SLA on queue change

Good day, I have successfully configured the SLA extension to apply SLA to new tickets within specific queues. I wonder if there is a way that I can apply a new SLA to an existing ticket on queue change. For example - ticket is created in queue Alpha and is automatically assigned an SLA

Re: [rt-users] error "could not find component" - upgrading to 4.4.0

nevermind, the problem was solved by updating /Ticket/Update.html Thanks On Mon, Jun 27, 2016 at 1:16 PM, Hugo Escobar wrote: > Hi, > > We are upgrading from 4.2.9 to 4.4.0 > > The error in the attached image results when attempting to upgrade a > ticket, > > url: >

Re: [rt-users] SLA Extension change SLA on queue change

Maybe the default only works when the SLA is blank in which case it wouldn’t work when you change queues. I guess you could try having very different names for the SLAs in each queue. -Original Message- From: Nicholas Adams [mailto:nick.adams...@gmail.com] Sent: 27 June 2016 17:24 To:

[rt-users] load Article in mail template

Hello, I want to include a dynamic advertisement-line into my autoreply (for new tickets) - something like the following: Dear ladies and gentlemen, Thanks your message - your ticket number is 123456 Best regards There should be about 5 advertisement-lines - when creating a new ticket, one

Re: [rt-users] Re-Display Ticket with added warning if owner changed during responding

On 6/27/16 1:38 PM, Jim Brandt wrote: Hey and thank you for your answer, I am using RT 4.4 <%init> warn 'set checks_failure => 1'; $checks_failure = 1; <%args> $checks_failure => undef I expected every update to fail, but when I add a reply the ticket is updated with "correspondence

[rt-users] apache setup in RT 4.4

I finished the setup of RT 4.4 now I am trying to enable the ldap authentication through apache then LDAPImport When I try to add the following in apache I get an error when restarting apache on AuthBasicProvider ldap should I be putting in the link to my ldap there or does the next line

Re: [rt-users] Re-Display Ticket with added warning if owner changed during responding

On 24.06.2016 14:19, Jim Brandt wrote: On 6/23/16 8:19 AM, David Schmidt wrote: Hello In case someone takes the ticket ownership wile I am composing a response I would like to redisplay the ticket (the submitted response shouldnt be deleted) and add a warning informing the user about the