Hi developer and user,
for ticket graphs you can set maximum depth to unlimit but this leads
to show only 6 levels of properties. This results in graphs where the
only property which is displayed for tickets above level 6 is the id,
which doesn't give you any useful information on this tickets.
Hi All,
I am trying to find out all tickets that are due in 48 hours and notify
through email.
I am using this in cronjob which runs hourly.
rt-crontool --search RT::Search::FromSQL --search-arg ( Status !=
'resolved' AND Status != 'rejected' ) AND ( Due '+48 hours' AND Due
'+49 hours')
On Fri, Sep 12, 2014 at 11:35 AM, Asif Iqbal vad...@gmail.com wrote:
Hi All,
I am trying to find out all tickets that are due in 48 hours and notify
through email.
I am using this in cronjob which runs hourly.
rt-crontool --search RT::Search::FromSQL --search-arg ( Status !=
'resolved'
Hi All
I have been playing around with RT for the last few weeks now and am trying
to import assets from an inventory I exported to a CSV file. The assets
successfully import but I am unable to fill the HeldBy field for any assets,
seeing the following warning when running the import ;
'Role
Hi,
I am new to RT. I have a test install of RT 4.2.6 on a RHEL 6.x platform. It
seems to work and I am newbie-lost in the universe of setting permissions --
but that is not currently my issue.
Our current helpdesk system has a bunch of queue-like things. I don't want to
have to click
A list member clued me in off-line: IMHO the RT::Queue Create docs leave a
lot to be desired. The argument in the title says Args but the description
says hash. Due to the way the Create function actually interpolates the
Args you can't pass a hash, as I understand the term. You instead
Check out also:
http://bestpractical.com/docs/rt/latest/initialdata.html
as this permits programmatic setup of a bunch of things, which might be
useful to slap into revision control/configuration management/etc.
On 13/09/2014 6:05 am, Karres, Dean kar...@illinois.edu wrote:
A list member clued
