Custom Query (11 matches)
Results (10 - 11 of 11)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#3 | fixed | Form for new users | ||
Description |
We need a form for new users to fill in. It has to check the chosen user name for validity and it has to calculate the password encryption. Along with this we need an e-mail address forge@… where the new users send the form response. |