> That way a user can individually grant attachment permissions on > different parent objects. Actually, thinking about it, this will > alleviate the need for an ATTACH permission altogether, as "CREATE" in > the wiki:attachment security realm would provide this permission. >
This could immediately provide a lot of workflow functionality, simply be declaring that assigning a ticket to a milestone requires ATTACH permission on the milestone, and the same for components, resolutions (WONTFIX/ASSIGNED/CLOSED/etc), and ticket owners. Whether hiding the options any given user doesn't have permission for is feasible I don't know, doing that many permission checks would be expensive. But checking permissions when the user tries to make a change would still be very useful. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
