Question

It would be nice to limit certain actions from users and/or groups individually.

Say for example, I have five project managers and only one of them I want to be responsible for adding projects. All PM’s should be able to create, edit, assign, resolve, & close cases. My development team I do NOT want them to have the ability to close cases, but they can create, edit, assign, & resolve. I think adding a new level of security/permissions would really help out with creating these sort of rules.

A list of a few attributes I would like to see:

ADMIN Type:

• Can manage GROUPS
• Can manage MAILBOXES
• Can manage PLUGINS
• Can manage PRIORITY
• Can manage PROJECTS
• Can manage SITE WORKING SCHEDULE
• Can manage SOURCE CONTROL
• Can manage WORKFLOW
• Can manage USERS
• Can manage WIKIS
• Can manage FILTERS
• Can edit TIMESHEET

CASE Type:

• Can CREATE cases
• Can EDIT cases
• Can RESOLVE cases
• Can CLOSE cases
• Can EMAIL from cases
• Can set case ESTIMATES
• Can edit case PRIORITIES

Answer 1

FogBugz always tries to walk the line between simplicity and power. Generally, we lean toward simplicity. It's not that the permissions themselves would be hard to implement or enforce, but that the permissions administration interface would make FogBugz much harder to use. Thus, the basic design principle is to trust the FogBugz user. If you can read, you can read everything you have access to. If you can edit, you can edit anything.

All edits are recorded, so there's full accountability and audit capability.

These kinds of fine-grained permissions are not planned for any future version of FogBugz.