What is better, one tracker for all projects, one tracker per project?
I am setting up Redmine for my department in which we have several software products. I am beginning to create one project per product, but I am now scratching my head as to what to do with the issue tracking...do I have one tracker for all projects or one tracker per project. What would be some pros and cons?
I have seen that a developer who is on multiple projects can see an aggregated list of all issues assigned to them, no matter which tracker they are in.
Another goal of mine is to have my management be able to see a complete list of issues, from all projects in one place instead of going from project to project.
Anyone have any advice as to how I should set up my tracker(s) for my projects?
RE: What is better, one tracker for all projects, one tracker per project? - Added by Nick Read about 11 years ago
Create one tracker for each issue "type" that you need to represent. For example, here on Redmine you have "Feature", "Defect" and "Patch".
At my work we have "Bug", "Feature" and "Internal Task", but we only apply the first two to projects that cover our products, and only use the last tracker for our single project dedicated to internal company tasks, eg, install firewall, reorganise shared document storage, ...
I wouldn't recommend creating a tracker for each project.
RE: What is better, one tracker for all projects, one tracker per project? - Added by Jason Morris about 11 years ago
Thanks for the advise. I have set up my trackers as you suggested and will give it a go. I like it so far.
Is there an easy way to transfer all tickets from one tracker to another one from within the UI? I see there is a way to do it one at a time, but that is a little time consuming.