[rt-users] ticket graph properties and unlimited depth
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. I think it don't make sense to display 100 property blocks if you have 100 linked tickets. I would propose to display only one property level if you set maximum depth to unlimit and apply this properties to all tickets. What do you think of this? Chris -- RT Training - Boston, September 9-10 http://bestpractical.com/training
[rt-users] Notify about tickets that are Due in 48 hours
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') --action RT::Action::NotifyGroup --action-arg ' a...@example.net' --transaction last --transaction-type comment Does this look kosher. I cannot tell if my Due settings is correct. I have read these two articles and still not sure if I am doing it right. http://bestpractical.com/docs/rt/latest/automating_rt http://requesttracker.wikia.com/wiki/TimedNotifications Do I have to use template? Thanks -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- RT Training - Boston, September 9-10 http://bestpractical.com/training
Re: [rt-users] Notify about tickets that are Due in 48 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' AND Status != 'rejected' ) AND ( Due '+48 hours' AND Due '+49 hours') --action RT::Action::NotifyGroup --action-arg ' a...@example.net' --transaction last --transaction-type comment Does this look kosher. I cannot tell if my Due settings is correct. I have read these two articles and still not sure if I am doing it right. http://bestpractical.com/docs/rt/latest/automating_rt http://requesttracker.wikia.com/wiki/TimedNotifications Do I have to use template? Thanks I am using rt 4.0.17 and perl/5.14.2 -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -- RT Training - Boston, September 9-10 http://bestpractical.com/training
[rt-users] Assigning HeldBy users during Asset Import
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 name HeldBy must be single-value for column Username, skipping' My current configuration is RT 4.27 with RT-Authen-ExternalAuth-0.21, Extension-LDAPImport-0.35, Extension-Assets-1.01 and Extension-Assets-Import-CSV-1.3. I have connected the ExternalAuth to my local AD and successfully imported all the domain users as unprivileged users. I am able to assign any of these users to the HeldBy role under the People tab of an Asset. Here is the snippet from RT_SiteConfig.pm for the field mapping I am using; Set( $AssetsImportUniqueCF, 'Key Number' ); Set( %AssetsImportFieldMapping, 'Catalog' = \'Keys', 'Name' = 'KeyNumber', 'Description' = 'EmployeeName', 'Status'= \'in-use', 'HeldBy'= 'Username', 'CF.Department' = 'Department', 'CF.Issue Date' = 'Issued', 'CF.Username' = 'Username', 'CF.Issued To' = 'EmployeeName', 'CF.Key Level' = 'KeyLevel', 'CF.Key Way'= 'Keyway', 'CF.Key Number' = 'KeyNumber', 'CF.Other Info' = 'Username', ); Is there something I am missing or is this function not available? In a related test, I am not able to assign a HeldBy user using the Bulk Update feature either. Thanks for any insight or solution to this. -- View this message in context: http://requesttracker.8502.n7.nabble.com/Assigning-HeldBy-users-during-Asset-Import-tp58502.html Sent from the Request Tracker - User mailing list archive at Nabble.com. -- RT Training - Boston, September 9-10 http://bestpractical.com/training
[rt-users] Programmatically create queues
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 through the GUI to create them all. I figured I would save time
by writing a small script that could create them all quickly. Apparently my
newbie understanding of RT in general applies to trying to code scripts too. I
looked at the existing ...rt4/sbin/... scripts and the html RT module docs and
came up with a one-liner (formatted over multi-lines for readability:
perl -e'use lib qw(/opt/rt4/lib);
use RT -init;
use RT::Queue;
use Data::Dumper;
my $queue = RT::Queue-new( RT-SystemUser );
$queue-Load(Public Printing);
$queue-Create({
Name=WWW,
Description=Web related issues,
CorrespondAddress=,
CommentAddress=,
InitialPriority=0,
FinalPriority=0,
DefaultDueIn=0
});'
However, when I run it I get:
[27849] [Fri Sep 12 17:56:10 2014] [warning]: Odd number of elements in hash
assignment at /opt/rt4/lib/RT/Queue.pm line 160. (/opt/rt4/lib/RT/Queue.pm:160)
[27849] [Fri Sep 12 17:56:10 2014] [warning]: Use of uninitialized value $name
in length at /opt/rt4/lib/RT/Queue.pm line 317. (/opt/rt4/lib/RT/Queue.pm:317)
Looking in the /opt/rt4/lib/RT/Queue.pm file shows the args hash (line 160 in
the 4.2.6 source) to have several more key tags available than the docs talk
about. Don't know if that is an issue.
What am I missing? My guess is something trivial.
Dean...K...
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
Re: [rt-users] Programmatically create queues
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 pass the
key value pairs, a la:
$queue-Create(
Name=WWW,
Description=Web related issues,
CorrespondAddress=,
CommentAddress=,
InitialPriority=0,
FinalPriority=0,
DefaultDueIn=0
);
Note, no curly braces.
-Original Message-
From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of
Karres, Dean
Sent: Friday, September 12, 2014 1:26 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Programmatically create queues
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 through the GUI to create them all. I figured I would save time
by writing a small script that could create them all quickly. Apparently my
newbie understanding of RT in general applies to trying to code scripts too. I
looked at the existing ...rt4/sbin/... scripts and the html RT module docs and
came up with a one-liner (formatted over multi-lines for readability:
perl -e'use lib qw(/opt/rt4/lib);
use RT -init;
use RT::Queue;
use Data::Dumper;
my $queue = RT::Queue-new( RT-SystemUser );
$queue-Load(Public Printing);
$queue-Create({
Name=WWW,
Description=Web related issues,
CorrespondAddress=,
CommentAddress=,
InitialPriority=0,
FinalPriority=0,
DefaultDueIn=0
});'
However, when I run it I get:
[27849] [Fri Sep 12 17:56:10 2014] [warning]: Odd number of elements in hash
assignment at /opt/rt4/lib/RT/Queue.pm line 160. (/opt/rt4/lib/RT/Queue.pm:160)
[27849] [Fri Sep 12 17:56:10 2014] [warning]: Use of uninitialized value $name
in length at /opt/rt4/lib/RT/Queue.pm line 317. (/opt/rt4/lib/RT/Queue.pm:317)
Looking in the /opt/rt4/lib/RT/Queue.pm file shows the args hash (line 160 in
the 4.2.6 source) to have several more key tags available than the docs talk
about. Don't know if that is an issue.
What am I missing? My guess is something trivial.
Dean...K...
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
Re: [rt-users] Programmatically create queues
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 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 pass the key value pairs, a la:
$queue-Create(
Name=WWW,
Description=Web related issues,
CorrespondAddress=,
CommentAddress=,
InitialPriority=0,
FinalPriority=0,
DefaultDueIn=0
);
Note, no curly braces.
-Original Message-
From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On
Behalf Of Karres, Dean
Sent: Friday, September 12, 2014 1:26 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Programmatically create queues
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 through the GUI to create them all. I figured I
would save time by writing a small script that could create them all
quickly. Apparently my newbie understanding of RT in general applies to
trying to code scripts too. I looked at the existing ...rt4/sbin/...
scripts and the html RT module docs and came up with a one-liner (formatted
over multi-lines for readability:
perl -e'use lib qw(/opt/rt4/lib);
use RT -init;
use RT::Queue;
use Data::Dumper;
my $queue = RT::Queue-new( RT-SystemUser );
$queue-Load(Public Printing);
$queue-Create({
Name=WWW,
Description=Web related issues,
CorrespondAddress=,
CommentAddress=,
InitialPriority=0,
FinalPriority=0,
DefaultDueIn=0
});'
However, when I run it I get:
[27849] [Fri Sep 12 17:56:10 2014] [warning]: Odd number of elements in
hash assignment at /opt/rt4/lib/RT/Queue.pm line 160.
(/opt/rt4/lib/RT/Queue.pm:160) [27849] [Fri Sep 12 17:56:10 2014]
[warning]: Use of uninitialized value $name in length at
/opt/rt4/lib/RT/Queue.pm line 317. (/opt/rt4/lib/RT/Queue.pm:317)
Looking in the /opt/rt4/lib/RT/Queue.pm file shows the args hash (line
160 in the 4.2.6 source) to have several more key tags available than the
docs talk about. Don't know if that is an issue.
What am I missing? My guess is something trivial.
Dean...K...
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
--
RT Training - Boston, September 9-10
http://bestpractical.com/training
