On Nov 20, 2014 5:49 AM, "Shawn Baker" <[email protected]> wrote:
>
> I recently upgraded from a Trac 0.11 server to 1.0.2.  I am seeing what I
think is weird behavior for ticket permissions.
>
> I have a "new" ticket that my user submitted (user1).  Trac is setup to
default the ticket ownership to a specific user (user2).  So user1 is the
reporter, but and user2 is currently owner of this ticket.  However, I have
the following ticket modification options available to user1:
> Leave as new The owner will remain user2.
> Accept. Next status will be 'accepted'.
> Reassign to <user drop down>. The owner will be changed from user2 to the
selected user. Next status will be 'new'.
> Requires more information and assign to <user drop down>. The owner will
be changed from user2 to the selected user. Next status will be 'needinfo'.
> Close as <resolution drop down>. The resolution will be set. Next status
will be 'closed'.
>
> These are the permissions for user1:
> TICKET_APPEND, TICKET_CHGPROP, TICKET_CREATE, TICKET_MODIFY, TICKET_VIEW
>
> This is the workflow for a ticket in this status:
> new_accepted = new,needinfo, reopened -> accepted
> new_accepted.default = 3
> new_accepted.name = Accept.
> new_accepted.permissions = TICKET_MODIFY
> new_needinfo = new -> needinfo
> new_needinfo.default = 1
> new_needinfo.name = Requires more information and assign
> new_needinfo.operations = set_owner
> new_needinfo.permissions = TICKET_MODIFY
> new_reassign = new -> new
> new_reassign.default = 2
> new_reassign.name = Reassign
> new_reassign.operations = set_owner
> new_reassign.permissions = TICKET_MODIFY
> leave = * -> *
> leave.default = 4
> leave.name = Leave
> leave.operations = leave_status
> closed = new,needinfo,reopened,open -> closed
> closed.default = 0
> closed.name = Close
> closed.operations = set_resolution
> closed.permissions = TICKET_MODIFY
> closed.set_resolution = wontfix,invalid,duplicate,limitation
>
> So, my question, am I missing something with Trac 1.0.2 to disallow users
from changing the status of tickets other than their own?
>
> Thanks for any help,
> Shawn

The behavior you are seeing looks like what I'd expect for the
configuration you've shown. There's nothing to limit the ticket workflow
actions to tickets for which the user is the owner. That would require a
plugin with a custom permissions policy. Nothing has changed in that regard
since 0.11 as far as I know.  I'll post an example shortly.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to