Best practices for organizing projects and workflows in MantisBT

[emilythomas266]

Hello everyone,

I’ve recently started using MantisBT to manage multiple projects and bug tracking for a small development team. Overall, it’s been very helpful, but I’m still trying to figure out the best way to structure everything for long-term scalability.

Right now, I have:

Separate projects for each client
Categories used for different modules/features
Custom fields for priority and environment details

However, I’m not fully sure if this is the most efficient setup as the number of issues grows. I’ve started noticing that reporting and filtering can become a bit messy when projects scale up.

I would really appreciate advice on the following:

Is it better to use fewer projects with more categories, or separate projects for each client/module?
What is the recommended approach for handling cross-project issues or shared components?
Are there any best practices for keeping workflows clean and manageable in larger teams?

If anyone has experience managing larger MantisBT installations, I’d love to hear how you structure your setup.

Thanks in advance for any suggestions!

[atrol]

Is it better to use fewer projects with more categories, or separate projects for each client/module?

Are clients allowed to view issues of other clients?