Thanks Matt!
I’ve been working on it, But I have no idea how to set up this!
I would like to use the something like “WHERE” clause to filter my results from Users (/html/helpers/Autocomplete/Owner) to show me only the Users who can be Owner.
I’d like to return only Users checked “Let this user access RT” and “Let this user be granted rights (Privileged)” on Create/Modify User page.
I’ve tried changing /share/html/Ticket/Create.html - Carbon60: Managed Cloud Services , but no lock!
I also tried changing line 72 in share/html/Ticket/Create.html from:
“…, Default => $ARGS{Owner}||$RT::Nobody->Id, …”
to each of these:
“…, Default => $ARGS{Owner}||12, 13,14 …” by Id…did not function as expected…
How to add a new arguments when the function was called?
At this point I can add my condition?
(/html/helpers/Autocomplete/Owner)
<%ARGS>
$return => ‘Name’
$limit => undef
$term => undef
$max => 10
</%ARGS>
Thanks,
Marcelo Calado.-----Original Message-----
From: Matt Zagrabelny [mailto:mzagrabe@d.umn.edu]
Sent: Thursday, November 12, 2015 10:09 AM
To: Marcelo Calado | TBS TAX Services mcalado@tbstaxservices.com
Cc: rt-users rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Owner Query - Custom
On Wed, Nov 11, 2015 at 10:21 AM, Marcelo Calado | TBS TAX Services mcalado@tbstaxservices.com wrote:
Hi,
I want to change (if possible) settings, under Permissions , modify the permissions that are allowed or denied for only the RT User’s to be Owner’s when I create a new ticket or modify?
The Watcher’s can’t be Owner!
Is it possible?
You can hack on:
share/html/Helpers/Autocomplete/Owners
I see there is only one callback in there. You could add another callback to the mason component and then have your code utilize that callback. BPS is usually pretty accepting to new callbacks - send a patch their way to (hopefully) get it included in upstream.
-m