All users too much permissions

hi all

how can i set it so that all users (unless specified otherwise) can not
see tickets that they do not own, currently when they log on they can
see “10highest priority tickets that i own” and also “10 newest unowned
tickets…” i would like to take away that second one.

one more thing

is there any way i can remove the “Quick Search” list from the right
hand side for all users except admins?

thanx

steve.vcf (774 Bytes)

hi all

how can i set it so that all users (unless specified otherwise) can not
see tickets that they do not own, currently when they log on they can
see “10highest priority tickets that i own” and also “10 newest unowned
tickets…” i would like to take away that second one.

You would have to disable any global options for SeeTicket (et al) and
configure it per-queue.

one more thing

is there any way i can remove the “Quick Search” list from the right
hand side for all users except admins?

See above… It would make more sense to just remove any global
options for SeeQueue than to bother customizing that form.

Andy Harrison

Steve,

I’m not sure why RT changed that in 3.2.2, it used to be that the bottom one was
"top 10 tickets I requested". We’ve actually changed that back for our group –
top 10 unowned tickets would be great for our manager, but even then, many
groups use RT.

copy $rtdir/share/html/Elements/MyRequests to
$rtdir/local/html/Elements/MyRequests and then make the following changes:

On or about line 47, change:
title => loc("[_1] newest unowned tickets", $rows),
to
title => loc("[_1] highest priority tickets I requested…", $rows),
On or about line 50, change
Format => “’<a href=”$RT::WebPath/Ticket/Display.html?
id=id">id/TITLE:#’, ‘<a href="$RT::WebPath/Ticket/Display.html?
id=id">Subject/TITLE:Subject’, QueueName, ExtendedStatus,
CreatedRelative, '<A HREF="$RT::WebPath/Ticket/Display.html?
Action=Take&id=id">".loc(‘Take’)."/TITLE: ’ ",

to
Format => “’<a href=”$RT::WebPath/Ticket/Display.html?
id=id">id/TITLE:#’, ‘<a href="$RT::WebPath/Ticket/Display.html?
id=id">Subject/TITLE:Subject’, Priority, QueueName, ExtendedStatus,
OwnerName ",

(Make SURE that’s all one line)

and on or about line 62, change
my $Query = “Owner = ‘Nobody’ AND ( Status = ‘new’ OR Status = ‘open’)”;
to
my $Query = “Requestor = '”.$session{‘CurrentUser’}->EmailAddress."’ AND (
Status = ‘new’ OR Status = ‘open’ )";

On or about line 52, we changed the sort order to be by priority by changing:
OrderBy => ‘Created’,
to
OrderBy => ‘Priority’,

I hope this is useful. Be sure to make the changes in the local directory.

-Sheeri Kritzer
Systems Administrator
University Systems Group
Tufts University
617-627-3925
sheeri.kritzer@tufts.edu

Quoting Andy Harrison aharrison@gmail.com:> On Wed, 19 Jan 2005 12:53:13 -0500, steve steve@n2sw.com wrote:

hi all

how can i set it so that all users (unless specified otherwise) can not
see tickets that they do not own, currently when they log on they can
see “10highest priority tickets that i own” and also “10 newest unowned
tickets…” i would like to take away that second one.

You would have to disable any global options for SeeTicket (et al) and
configure it per-queue.

one more thing

is there any way i can remove the “Quick Search” list from the right
hand side for all users except admins?

See above… It would make more sense to just remove any global
options for SeeQueue than to bother customizing that form.


Andy Harrison


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

RT Administrator and Developer training is coming to your town soon! (Boston,
San Francisco, Austin, Sydney) Contact training@bestpractical.com for
details.

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Steve,

I’m not sure why RT changed that in 3.2.2, it used to be that the bottom one was
"top 10 tickets I requested". We’ve actually changed that back for our group –
top 10 unowned tickets would be great for our manager, but even then, many
groups use RT.

Just create different ones and add them to the index.html form, you
don’t need to sacrifice any.

Here’s my way of doing different ones for different departments.

% # create an empty group obj
% #
% my $GroupObj = RT::Group->new( $session{ ‘CurrentUser’ } );
% #
% # Load the current user into a principal obj for group check
% #
% my $PrincipalObj = RT::Principal->new( $session{ ‘CurrentUser’ } );
% $PrincipalObj->Load( $session{ ‘CurrentUser’ }->id );
% #
% # Load the group for which you want to check membership
% #
% $GroupObj->LoadUserDefinedGroup( ‘Network’ );
% my $HasMemberNetwork = $GroupObj->HasMemberRecursively( $PrincipalObj );
% #
% # and again with a different var for the results
% #
% $GroupObj->LoadUserDefinedGroup( ‘Sysops’ );
% my $HasMemberSysops = $GroupObj->HasMemberRecursively( $PrincipalObj );
% #
% # Don’t bother displaying the regular MyRequests for these folks
% #
% unless ( $HasMemberNetwork or $HasMemberSysops ) {
<& /Elements/MyRequests &>


% }
% #
% # Display the custom ones based on the results of the group check
% #
% if ( $HasMemberNetwork ) {
<& /Elements/NetworkRequests &>
% }
% if ( $HasMemberSysops ) {
<& /Elements/SysopsEMORequests &>
<& /Elements/SysopsTasksRequests &>
% }

Andy Harrison