Hi List,
am I right when I say that the right to merge tickets is included in
the right modify tickets (at least in RT 3.6.7)? Therefore there is no
easy way to prevent the user of merging tickets? Is there maybe another way?
Thanks for an quick answer.
Violetta
--
Hi,
when you are on the RT At A Glance site you see your highest priority
tickets and on the right hand site an edit. Follow it and on the new
page follow Search - My Tickets, add stalled to your search save it.
That should do.
Regards,
Violetta
Reginaldo Russinholi schrieb:
Hi all,
Is
Hi,
yes I am doing that already, but they add the days to the current date
and not the Created date. Does anyone actually know how I can tell the
perlthing to use the created date and not the current date. That would
be very helpful.
Thanks.
Violetta
Ruslan Zakirov schrieb:
Look into
Hi,
can anyone tell me how I can set Due depending on the Created-Date?
I know how to get the the Creationdate:
my $createdate = ($self-TicketObj-CreatedObj);
But how can I encrease it for example 14 days?
I did find something that takes the scrip execution time and adds 1 day.
Hi Gene,
good idea, thanks. But didn't work either. The scip is than always
applicable and always applies the customfield which it should not do. *args*
I also tried unless, but than I get the errormessage:
Scrip 17 IsApplicable failed: syntax error at (eval 950) line 1, near
-Subject unless
Hi,
you don't need create. For that you also user correspond.
Regards,
Violetta
Monti gmail schrieb:
Hi there,
sorry to nag but I'm despaired to find a solution for a basic which should
be common problem/need.
I need the ability to create ticket from email.
mailgate provides only
Hi Rene,
brauch mal dringend hilfe vom perlguru. ich möchte was abfrage und zwar
wenn ich im subject akut *nicht* drinnen steht dann solls zutreffen
$self-TicketObj-Subject !=~ /[A|a]kut: / -- tut nicht
$self-TicketObj-Subject !~ /[A|a]kut: / -- tut nicht
wie muss das denn richtig heissen
Hi,
if ($self-TransactionObj-Type eq Create
($self-TicketObj-Subject !=~ /[P|p]roje[c|k]t: / ||
$self-TicketObj-Subject !=~/[A|a]kut: / ) )
I'm pretty sure that is a higher precedence than ||, so the result
without parentheses would be the same as ( ( A B ) || C ) instead of
sorry, the german mail was not meant for the mailinglist *args*
--
Vorstand/Board of Management:
Dr. Bernd Finkbeiner, Dr. Florian Geyer,
Dr. Roland Niemeier, Dr. Arno Steitz, Dr. Ingrid Zech
Vorsitzender des Aufsichtsrats/
Chairman of the Supervisory Board:
Prof. Dr. Hanns Ruder
Sitz/Registered
Hi,
has anyone a scrip or an idea how my condition for the following
situation has to be written?
My customfield called CFA has for example the value value1 and
value2. The value is currently set to value1. I now want my scrip to
check wheather the value has changed and to which value it has
Hi,
I have different scrips that check for certain words in the subject line
and the code looks for example like that:
if ($self-TransactionObj-Type eq Create
$self-TicketObj-Subject =~ /[A|a]kut: / )
--snip--
so, if the subject contains akut do something.
That works.
What I now want to
my code looks like this:
if ($self-TransactionObj-Type eq Create
$self-TicketObj-Subject !=~ /[P|p]roje[c|k]t: / ||
$self-TicketObj-Subject !=~/[A|a]kut: / )
--snip--
sorry, for bothering you. it actually works, the problem was something
else in my code which prevented my scrip to run
Hi Dave,
in my test-rt (3.6.1, which still has all the defaults configured) is a
global scrip that says:
On Correspond Open Tickets with template Blank
are you sure you haven't got it?
Regards
Violetta
On all of our queues when a ticket is in a resolved state and a user
makes a comment on
Hey Kenn,
If you have a scrip that modifies ticket data that is ALSO set by
default RT code, you need to make the STAGE of the scrip in batch
mode. That should do it. I've had that problem before and that fixed it.
No it doesn't :-/ Still thank you for your help.
Any other idea,
Hey,
My queustion is the following. I have a queue where the default for the
due date is set to 7 days. I have different scrips that set the due date
to either 1 or 14 if the subject contains certain key words.
As I understand RT, as soon as a ticket comes in the defaults in the
basics will
Dear Gabriel,
it appears to me like the only way to do this is to carefully
plan out exactly in which order you create the custom fields so that
they appear on the tickets in the order they were created?
I hope I understood you correctly. I am using RT 3.6.1 and I haven't
seen a later
Hi,
Dashboard, Queue and Ticket. Should it be translated or should it be
like it is?
My experience is that it makes it easier not to translate Queue and
Ticket. I myself find it very confusing to explain anything to my
RT-Users about Stapel and not Queue. So, at least stay with Queue and
Hello,
We are using RT 3.6.1 and we have different Queues with exactly the same
CustomFields with exactly the same CustomFieldValues like
Queue1:
CustomField1: Platform
CustomFieldValues1: Linux
CustomFieldValues1: Windows
Queue2:
CustomField2: Platform
CustomFieldValues2: Linux
18 matches
Mail list logo