Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See DemoClose
i didn't see a way to attach this to any of the existing roles posts - so I made a new one.
Attached is my take on the many roles feature requests seen on the features list.
Some new role-related files, and some updates to editing bugs, users, etc.
Run the sqlupdate.sql script on your bugtracker.net DB (back it up first :) to create/alter the appropriate DB tables.
A summary of features:
1) Admin menu now has roles option. Roles can be added and specific statuses can be selected to apply to those roles.
2) Editing a user a default role can be assigned to that user.
3) User project permissions can also have roles set on a per-project basis. This can be done from the admin's 'edit user' screen, or the project's 'edit user permissions' screen
4) Added 'role' column to user list in admin section.
When creating or editing bugs, only the statuses you have access to (either by default, or inside that project) can be selected. Should a user have created a bug with a status you don't have access to - but it's assigned to you - the option of '[current status]' is selected by default. This allows you to make changes to the bug without having to set it to a status you have access to that may not be appropriate (i.e. a PM assigns a bug to a sales person for more info, but that bug is 'in process' and sales people only have access to the statuses of 'new' and 'on hold' - the sales person can answer the question and give it back to someone without changing status).
The SQL script will also create an 'Admin' role, give it access to all statuses, and assign it to every user. This is so your btnet install does not break because users must be assigned a role. This will give them the same functionality they have now (the ability to assign all statuses) and then you can create alternate roles and assign them to users.