---
** [tickets:#7985] Explain private ticket permissions better**
**Status:** open
**Milestone:** unreleased
**Created:** Tue Sep 08, 2015 08:19 PM UTC by Dave Brondsema
**Last Updated:** Tue Sep 08, 2015 08:19 PM UTC
**Owner:** nobody
Each tool should be able to add its own content at the top of the
`app_admin_permissions.html` template
The ForgeTracker tool should say something like this:
> If a ticket is marked as private, only Developers (and Admins too, of course)
> will have permission to access and change it. Everyone else will be denied
> all permission, including read access. Users that are developers will have
> permission to do only what the Developer permission grants them (and grants
> inherited via \*authenticated and \*anonymous, e.g. 'read'); they won't have
> their normal permissions that they have with regular tickets.
Perhaps also mention how the special permissions take effect when the ticket is
made private, so changing what permissions Developers have later won't change
the ticket's permissions. Adding or removing people from the Developers role
will still work though.
---
Sent from forge-allura.apache.org because [email protected] is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
