Hello,
I have a (happily) running RT 3.6.5 with approx 300,000 tickets in it and a
database of size of around 9 Gig (lots of attachments sadly). I have the
application upgraded, but when I try and run the schema upgrade in my test
environment it is taking forever (for values of forever which e
Hi All,
I have investigated the possiblility of having the trigger rule out one of
these transactions. I have now come up with the below ammendment which I
feel should work but we now get a total of 0 emails sent so I feel it is
flawed. Any ideas?
*
CODE:*
my $txn = $self->TransactionObj;
return
Hi Ken,
thank you for your answer
Kevin Phair wrote:
>
> For the above idea, you can try this:
> http://code.google.com/p/asset-tracker-4rt/wiki/HowToLinkTicketToAssetScrip
>
> In theory, you add a ticket custom field, and the user can then just
> stick in the name of an asset and the ticket
who else wrote:
>
> Sounds like a plan :-) Which version of RTx-AssetTracker are you using? I
> can only find 1.2.3, not 1.2.4b1; anybody got a download link?
You can grab it out of their subversion repo, something like:
svn checkout http://asset-tracker-4rt.googlecode.com/svn/at/tags/1.2.4b1
a
Hi,
Kenneth Marshall-3 wrote:
>
> In the same vein, you can use the RTx-AssetTracker to group the same
> information
> using Asset custom fields and attach the asset to the ticket(s) in
> question. We
> are working on doing this with users machines, sofware and other types
> of assets. You
who else wrote:
> After dealing a bit with RT and checking out quite a lot of posts in this
> list, i come up with my scenario which would suit me best, perhaps
someone
> out there has done something similar:
>
> We need to do support for clients, which have usually more than one
contact
>
Quoting Julian Hein :
> Hi,
>
> You could just create a Queue "Customers" and create a ticket for every
> customer there and than attach all the info you have to custom fields and
> attachments. The Companies people could be CCs on this tickets.
>
> All you need to do then is create a script that
Hi,
You could just create a Queue "Customers" and create a ticket for every
customer there and than attach all the info you have to custom fields and
attachments. The Companies people could be CCs on this tickets.
All you need to do then is create a script that links this ticket to any new
ticket
Hi there,
after reading the chapter about custom fields in "RT Essentials" i thought,
setting rights on the custom field, like this:
everybody "show custom field"
privileged "show custom field"
privileged "edit custom field"
could do the trick, but no way, the error won't go away.:-(
Best
w_
After dealing a bit with RT and checking out quite a lot of posts in this
list, i come up with my scenario which would suit me best, perhaps someone
out there has done something similar:
We need to do support for clients, which have usually more than one contact
to communicate with us and more th
10 matches
Mail list logo
