On Tuesday, November 18, 2014 10:51:08 PM UTC-8, RjOllos wrote: > > On Tuesday, November 18, 2014 10:34:58 PM UTC-8, Patrick Schaaf wrote: >> >> > 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. >> > This could be a good feature to support. If we don't implement the ability > to put a permission in the set_owner field then you'd have to make sure > that all users with TICKET_MODIFY share a group or set or groups that each > have the TICKET_MODIFY permission. This could be extremely simple or very > complicated depending on the data in your permissions table. >
Trac #11839 has been resolved - permissions and groups can be included in the comma-separated list of the `set_owner` workflow attribute. Trac 1.1.3 will be released in a few days. Please let us know if you are able to try out the new feature, and if you see any deficiencies in the implementation. I briefly documented how to upgrade from the GroupingAssignToPlugin, but more detailed information might be useful: http://trac-hacks.org/wiki/GroupingAssignToPlugin?action=diff&verion=7&old_version=4 -- 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.
