[rt-users] status of Steal Ticket feature?

[Jesse Vincent]

 From the UPGRADING file in the distribution:

*******

UPGRADING FROM 3.5.7 and earlier - Changes:

Scrips are now prepared and committed in order alphanumerically by  
description.
This means that you can prepend a number (00, 07, 15, 24) to the  
beginning of
each scrip's description, and they will run in that order.  Depending  
on your
database, the old ordering may have been by scrip id number -- if  
that is the
case, simply prepend the scrip id number to the beginning of its  
description.


UPGRADING FROM 3.5.1 and earlier - Changes:

The default for $RedistributeAutoGeneratedMessages has changed to
'privileged', to make out-of-the-box installations more resistant
to mail loops. If you rely on the old default of redistributing to
all watchers, you'll need to set it explicitly now.


UPGRADING FROM 3.3.14 and earlier - Changes:

The "ModifyObjectCustomFieldValues" right name was too long. It's  
been changed to
"ModifyCustomField"


UPGRADING FROM 3.3.11 and earlier - Changes:

= Rights Changes =

Custom Fields now have an additional right "ModifyCustomField".
This right governs whether a user can modify an object's custom field  
values
for a particular custom field. This includes adding, deleting and  
changing values.


UPGRADING FROM 3.2 and earlier - Changes:

= Rights changes =

Now, if you want any user to be able to access the Admin tools (a.k.a.
the Configuration tab), you must grant that user the "ShowConfigTab"
right.  Making the user a privileged user is no longer sufficient.

"SuperUser" users are no longer automatically added to the list of  
users who can own tickets in a queue. You now need to explicitly give  
them t
he "own tickets" right.




On May 17, 2006, at 5:23 PM, Joshua Colson wrote:

> On Wed, 2006-05-17 at 17:16 -0400, Joe Auty wrote:
>> Hello,
>>
>> I've set my users with global superuser permissions, but for some
>> reason this wasn't enough to own a ticket. I set them with own
>> permissions, and now they can be assigned tickets.
>
> I can confirm this also. I have a SuperUser (using RT 3.6) who is  
> unable
> to take ownership of a ticket. If I assign the OwnTicket right to the
> user then it works. I just hadn't gotten around to digging deeper for
> (what I'm assuming is) a bug.
>
> -- 
> Joshua Colson <jcolson at voidgate.org>
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
>
> We're hiring! Come hack Perl for Best Practical: http:// 
> bestpractical.com/about/jobs.html
>