Custom Query (11 matches)
Results (7 - 9 of 11)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8 | fixed | distinct admin access | ||
| Description |
Some projects will not want to give all their developers full admin access. Change to three levels of access: user (as now), developer (all but TRAC_ADMIN), TRAC_ADMIN. The admin access is irrelevant to svn and hence also to the script that composes the authz file from the trac permissions. All we need is to change the developer group of permissions to be user plus what they need, but not as much as to have the admin button in the wiki. |
|||
| #10 | fixed | date format wrong (American) | ||
| Description |
Dates are displayed in the rather confusing mm/dd/yy format. |
|||
| #11 | fixed | permission group "ticket" | ||
| 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. |
|||
