Opened 17 years ago
Closed 17 years ago
#11 closed enhancement (fixed)
permission group "ticket"
| Reported by: | AndyVick | Owned by: | Horst Meyerdierks |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | trac | Version: | |
| Keywords: | Cc: |
Description
In one or more projects it may be useful to give anon access to reading the wiki and making tickets, whilst keeping tabs on repository access by giving the user group of permissions only to known registered users. So this would need another group of permissions "ticket". The "user" group of permissions would remain as is, and the "ticket" group of permissions would be the same, except that it gives no access to the repository. Typically, projects could then give the user anonymous the ticket group of permissions, while reserving the user permissions to known users. Although they could equally have three levels of access: developer, user, and ticket, each with known users only.
Change History (2)
comment:1 by , 17 years ago
| Status: | new → assigned |
|---|
comment:2 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I have added to all existing projects the new permission group "ticket". This will also be added when new projects are created. The "ticket" group of permissions is the same as "user", but without BROWSER_VIEW and CHANGESET_VIEW. The script that every hour calculates SVN access from trac access is unchanged, i.e. it ignores the "ticket" group and hence no SVN access is given to the "ticket" group. When you go into the trac Admin you will find "ticket" alongside "developer" and "user", use it in the same manner. "user" access is a superset of "ticket", there is no need to give a user "ticket" access in addition to "user" or "developer" access.