0022336: Assign projects to client with access to only one project - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0022336	mantisbt	plug-ins	public	2017-02-08 00:55	2017-02-26 21:18

Reporter	tejaswini.hedawoo	Assigned To	atrol
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	no change required
Product Version	2.0.1

Summary	0022336: Assign projects to client with access to only one project
Description	I want to assign a project to our client with access to only one project and they should not able to view other projects created in Mantis. Is there a way I can do this?
Additional Information	All our projects are public projects and can't change it to private now I tried creating user group, but don't see feature to create that in Mantis 2.0.1
Tags	No tags attached.

atrol 2017-02-08 02:02 developer ~0055570	Using private projects is the right approach for it. Having user groups is a known feature request, see 0003444 for it.

tejaswini.hedawoo 2017-02-10 00:25 reporter ~0055628	My all other projects are public projects which are for internal group.Even if i create 'Private' project for clients, then also they can view other projects in the list, which we don't want. In this case i have to make all projects 'private' which is very time consuming for me. Do you have any other solution to my problem.

cproensa 2017-02-10 03:24 developer ~0055632	Do you have any other solution to my problem. I manage a mantis instance for multiple groups, and all projects must be private to get that scenario. The definition of "public" projects is that there is no special access list, apart from general access level permissions for viewer, reporter, etc.

atrol 2017-02-10 03:34 developer ~0055634	i have to make all projects 'private' which is very time consuming for me. What does "very time consuming" mean? Are you aware that you can copy users from project P1 to project P1

atrol 2017-02-21 02:40 developer ~0055725	tejaswini.hedawoo, You did not provide any feedback and your feature request is covered by 0003444. I am therefore resolving this issue as "no change required".