Changes to allow selecting a requestor from drop downlist

I’d be quite curious to see a version that uses livesearch to 1)
not

break the experience for users without javascript and 2) doesn’t
build a

list of every user in the system for every page with a select
requestor

widget.

By livesearch, are you referring to some implementation of AJAX?

No, I guess AJAX requires JS as well.

But, you see, it doesn’t break for users who don’t have
javascript.

Oh. Ok. You did mean “some implementation of AJAX”. :slight_smile:

I was looking into that idea as well, but I’m not an AJAX master.
Hopefully, someone who is will get itchy for that before me.

Cheers,
– jra

Hmm, Somehow I missed most of this thread, but then, I’m traveling on
business. I had originally written this stuff over a year ago, but
after replacing a couple of machines, I found that I didn’t have it when
it was time to build the new RT instance, so I just whacked it together
again.

I’m not sure what “livesearch” is, and I guess I sort of thought that
this did fit into AJAX, but I haven’t had time to read up much about
AJAX (I have some nifty sites bookmarked though! ;>). Anyway, this one
works fine for us, I’d be happy to see an improved version though…

-Kelly

Kelly,

Awesome little modification this. Love it. The one thing I am trying
to get to grips with is, presently it can only have requestors from the
Privileged user set (or at least that’s the effect I am getting).

How would I allow it to also view non-privileged users (i.e. ppl who
would be presented with the Self-Service interface if they logged in
themselves)?

Thanks heaps mate.

BenR

[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kelly F.
HickelSent: Thursday, 18 August 2005 3:53 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Changes to allow selecting a requestor from drop
downlist

I just put on the wiki a set of changes to allow call center folks to
chose a requestor from a drop down list when creating a ticket, as
opposed to typing in the email address. It’s at the URL below in case
someone else can use it.

http://wiki.bestpractical.com/index.cgi?SelectRequestor

Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh@mqsoftware.com

Ben,

        Well, the line below with WhoHaveRight limits the list of

users to those that can create tickets. In my setup, that’s everyone.
You’d need to limit this in a way that would fit your situation…

my $Users = RT::Users->new($session{CurrentUser});
$Users->WhoHaveRight(Right => ‘CreateTicket’, Object => $object,
IncludeSystemRights => 1, IncludeSuperusers => 0);
while (my $User = $Users->Next()) {

Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh@mqsoftware.comFrom: Ben Robson [mailto:ben.robson@classicblue.com.au]
Sent: Tuesday, August 30, 2005 11:33 PM
To: Kelly F. Hickel; rt-users@lists.bestpractical.com
Subject: RE: [rt-users] Changes to allow selecting a requestor from drop
downlist

Kelly,

Awesome little modification this. Love it. The one thing I am trying
to get to grips with is, presently it can only have requestors from the
Privileged user set (or at least that’s the effect I am getting).

How would I allow it to also view non-privileged users (i.e. ppl who
would be presented with the Self-Service interface if they logged in
themselves)?

Thanks heaps mate.

BenR

From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kelly F.
Hickel
Sent: Thursday, 18 August 2005 3:53 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Changes to allow selecting a requestor from drop
downlist

I just put on the wiki a set of changes to allow call center folks to
chose a requestor from a drop down list when creating a ticket, as
opposed to typing in the email address. It’s at the URL below in case
someone else can use it.

http://wiki.bestpractical.com/index.cgi?SelectRequestor

Kelly F. Hickel
Senior Software Architect
MQSoftware, Inc
952.345.8677
kfh@mqsoftware.com