<div class="gmail_quote">On Thu, Sep 2, 2010 at 3:47 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Sep 2, 2010 at 3:04 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
</div><div class="im">> 1) Trac users cannot assign themselves their own tickets (this should be<br>
> enforceable through Trac, hopefully once Otto fixes associating tickets with<br>
> actual Trac usernames, rather than "themetracbot")<br>
<br>
</div>This turns out to be trickier than it seemed at first. So, it might<br>
take me a while, don't expect quick turnaround.<br>
<br>
Expect me to make a test ticket or two when trying this out. Just ignore them.<br>
<div class="im"><br>
> 2) keywords can only be modified by admins (we don't need to be modifying<br>
> these ourselves anyway, do we?)<br>
<br>
</div>Trac considers priority, assignment, keywords, etc to all be part of<br>
the same set of permissions. Exceptions: description field and cc<br>
field have their own permissions.<br>
<br>
Only way I can think of preventing this problem is to define who is a<br>
reviewer. This can be done, but it requires management by an admin to<br>
add/remove permissions from users (actually, you can use a reviewer<br>
group mechanism, but you still have to be an admin to do it).<br>
<br>
If you want to create a reviewers group and remove the ability of<br>
normal users to resolve tickets (reserving that to the reviewers<br>
group), well then that's something ya'll have to decide.<br>
<br>
You can see the full list of trac permissions and how they work here:<br>
<a href="http://trac.edgewall.org/wiki/TracPermissions" target="_blank">http://trac.edgewall.org/wiki/TracPermissions</a></blockquote><div><br></div><div>Hmm, perhaps a "Reviewers" group with custom permissions is the best/easiest way to go?</div>
<div><br></div><div>Then, everyone else can only add comments to tickets, and not change their status/keywords/owner/etc.</div><div><br></div><div>What does everyone else think?</div><div><br></div><div>Chip </div></div>