> In our deployment, we use the convention > * usernames are all lower case > * Group_Names are mixed case > * PER_MISSIONS are ALL uppercase
Had a look at what I actually did in GroupingAssignToPlugin three years ago. It is: * anything all-lowercase is conidered a username, and not recursively checked * anything else is recursively resolved So, I could, in addition to the Group_Names I actually use, also put some PER_MISSIONS into the workflow step .owner_group setting, like .owner_group = TICKET_MODIFY, and have it populate the box with all users having that permission. Again, just noting the differences to your implementation - you are infinitely better suited to judge what's the "tracky" way of doing it :) best regards Patrick -- 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.
