I am readying my engineering team to move over to Mantis from a home grown internal system that is nolonger manageable/supportable. I have been a supporter of Matis solution over several years though use in other business projects.
In getting ready for this move to Mantis I created a feature comparison matrix. This highlighted one missing major feature which we rely on heavily at my company. This posting is an attempt to discover how to access a possible well hidden feature in Mantis or to ask if this is on the current feature roadmap or to get advise on how such a feature could be implemented within the current framework for the benefit of the product.
Feature
=====
Our current system is both used internally and customer facing. Our customers have the ability in our current system to report new bugs and track those same bugs as well as see the state of issues/bugs which we have made visible to them.
The way in which this works is that each user belongs to a group. The default group is the bug system owner (us). By default any bug created is made visible to the default group and the reporter's group (which may be the same). In addition any member of the default group at a specific role/level or higher, has the ability to make any bug when created or at any later time visible to any number of other groups.
What this implies is that for any given project/product all bugs are viewable by the default group. For any given project/product though there may be bugs that were created by a member of the non default group and is therfore additionally viewable/trackable by members of that group. Lastly, there may also be bugs that have been made visible to one or more other groups my a default group member.
I know this sounds complex, however we have found this a very powerful feature of our current system.
Any one's thoughts on this subject would be gratefully appreciated.
Selective visibility of bugs in project, to users/groups
Moderators: Developer, Contributor
Mantis is designed with the concept of access levels rather than user groups, although user groups is being raised every now and then and will probably make it into the product one day. However, it will probably map to what a user account can be setup to do at the moment.
The way I found similar functionality implementd using Mantis is as follows:
1. Issues can be submitted as private by default.
2. Your engineering team can have the required access level to view private issues.
3. Reporters can be allowed to view their own issues.
4. Reporters are able to see public issues.
You control what these reporters can see by selectively changing some of the issues to public. But once you do that, these issues will be visible to all reporters that have access ot the project.
This may not exactly match your requirement, but it will probably be close to what you need.
Regards,
Victor
MantisConnect
http://www.futureware.biz/mantisconnect
The way I found similar functionality implementd using Mantis is as follows:
1. Issues can be submitted as private by default.
2. Your engineering team can have the required access level to view private issues.
3. Reporters can be allowed to view their own issues.
4. Reporters are able to see public issues.
You control what these reporters can see by selectively changing some of the issues to public. But once you do that, these issues will be visible to all reporters that have access ot the project.
This may not exactly match your requirement, but it will probably be close to what you need.
Regards,
Victor
MantisConnect
http://www.futureware.biz/mantisconnect
-
ghirardelli
- Posts: 2
- Joined: 17 Mar 2006, 16:47
- Location: France
Hi,
I have the same needs, i think.
Different developers work on a same project, but i have to hide bugs between the different developpers. Only managers can see all the bugs.
Using private functionalities, bugs reported by one developer are not visible by the other developers. This looks great, but there is a major problem: if i assign a bug to a developer (as manager, or administrator), this developer cannot see it.
So how can i authorize developers to see the bugs that they have reported AND the bugs where they are assigned ???
Any help ?
I have the same needs, i think.
Different developers work on a same project, but i have to hide bugs between the different developpers. Only managers can see all the bugs.
Using private functionalities, bugs reported by one developer are not visible by the other developers. This looks great, but there is a major problem: if i assign a bug to a developer (as manager, or administrator), this developer cannot see it.
So how can i authorize developers to see the bugs that they have reported AND the bugs where they are assigned ???
Any help ?
I'd really like to figure out how to make it so that only those with high enough permissions to see "private" bugs could report an issue with that setting, otherwise the setting would be 'public'.
So all reporters would only be able to write 'public' bugs, in other words, if they dont have the acess level to see a 'private' bug, then when reporting a bug they wouldnt have access to the setting anyway but it would default to 'public'. Everyone else with higher permissions than that would by default write 'private' bugs, according to the "$g_default_bug_view_status" setting in my config_inc.php file (currently with our setting, 'reporters' will by default write "private" bugs, so others with reporter permissions cant see their bugs). They would have to manually set the 'public' flag.
This would make a nice shield to let our beta team see each others bugs but not be able to see engineering's bugs. Currently we just have our projects private and all the bugs public by default, but we want to change it to let the reporters view only each others bugs.
So all reporters would only be able to write 'public' bugs, in other words, if they dont have the acess level to see a 'private' bug, then when reporting a bug they wouldnt have access to the setting anyway but it would default to 'public'. Everyone else with higher permissions than that would by default write 'private' bugs, according to the "$g_default_bug_view_status" setting in my config_inc.php file (currently with our setting, 'reporters' will by default write "private" bugs, so others with reporter permissions cant see their bugs). They would have to manually set the 'public' flag.
This would make a nice shield to let our beta team see each others bugs but not be able to see engineering's bugs. Currently we just have our projects private and all the bugs public by default, but we want to change it to let the reporters view only each others bugs.