Mantis Bug Tracker - Forums

Hello,

I am looking for some experience with mantis for "managing" many projects ... in hundreds range.

Especially I am looking for:
- if there are any stability issues
- organizing projects (subprojects?)
- user rights (groups access rights)

Thanks for any information.

PKY

Hi pky!
Here i'm using the Mantis with tree big projects and segregate these in subprojects according the subversions of the project
Actually I have 17 projects (subprojects) on Mantis.

The user rights have a little rule...
- Projects in development have restrict access to developers, testers and project managers for these project, other users of don't work in these project don't have acess. The project is alter to private for this.
- When the project is finished, this come back to status 'public', and everybody can access all the project

Regrads,
Elias Nogueira

eliasn wrote:Hi pky!
Here i'm using the Mantis with tree big projects and segregate these in subprojects according the subversions of the project
Actually I have 17 projects (subprojects) on Mantis.

The user rights have a little rule...
- Projects in development have restrict access to developers, testers and project managers for these project, other users of don't work in these project don't have acess. The project is alter to private for this.
- When the project is finished, this come back to status 'public', and everybody can access all the project

Regrads,
Elias Nogueira

Thanks for your experience sharing. I think of using mantis with 200 to 300 projects. Many of them would be only simple task list, but some of them would be fully featured, with sub-projects.

So anyone with many,many projects in mantis?

Regards, PKY

My company use mantis with more than 100 different projects, and it works very well.
You can make subproject without any problems.
You can set users rights as you want :
-You create a user with a default right (for ex developer). He will have this right on all public projets, until you have not redefine them in a particular project (by "add users to a project").
-At the beginning, he will not see the private projects. If you want him to participate to a private project, you 'll have to add him manually to this project.

So, if you have 3 projects: A, B (publics) and C (private), user U with developper rights have developer rights in A and B, but will not see project C (because private).
If you add this user to project B with manager rights, he will be manager for project B only.
In order to make this user see project C, you will have to add him manually.

So, it is possible to make users only see the projects in which they work.