From: Glenn H. <thr...@ma...> - 2005-04-06 16:35:56
|
This is possible with the new threshold code in 1.0.0. You should be able to define a new access level (client). You can then make "client" the only level that can do some things using the syntax: $g_some_threshold = array( CLIENT ); You can also do this through the new UI where available. (Note, I would still give ADMINISTRATOR permissions to do everything. It's nice to be able to undo what someone accidentally did without resorting to an SQL editor). ... Glenn On 4/1/05 1:31 PM, "Russ Tennant" wrote: > > Is there a way to give permission to a user to change some bug properties > but not have the ability available to developers, managers, and > administrators? I'd like to create another type of user called "client" or > something similar that has the ability to use / change statuses or custom > fields that no one else has access to. The idea is that we want to give our > clients the ability to approve / reject new features and accept fixed bugs > before they are resolved. We do not want developers or managers to have the > ability to change the "client" properties and at the same time we do not > want to give our clients the same ability as developers or managers. A list > of user types follow in order of increasing ability as we would like to use > them. > > viewer > reporter > updater > *client* (can do some things that developers and managers cannot do) > developer > manager > administrator > > > Is this possible with mantis? Has anyone developed something similar? > Thanks. |