Projects sharing bug numbers? Any plugins?

Added by Jonathan Hight almost 14 years ago

Greetings everyone,

I have stumbled into a problem using Redmine for a multi-project game development database. Additional projects tend to increment all bug #'s in the database when I/we do not need them to. Ever.

For example: Proj. A bug # is 10, Proj. B bug # is 11.

This makes it painstakingly hard to track # of issues between databases when they are assigned to other people and is going to cause a lot of confusion to some of our not so bug tracking savvy individuals who will be using the database.

Is there any way around this?

We will never have a use for tracking the same bug in multiple databases. We will simply copy or create a new bug and add a note or additional info to it. Each database needs to be truly separate from the other, while still being able to remain in the same app/website for management purposes.

Any help would be much appreciated.

P.S. Is there anyway to reset the bug # values and start them over incrementing. We currentlyt have a large amount of issues now out of sync, as I did not know this would occur(ive never used a bug database that had this issue before).

Thank you,

Replies (1)

RE: Projects sharing bug numbers? Any plugins? - Added by Timothy High almost 14 years ago

It sounds like what you need is a separate installation of Redmine for each project. That should be easy enough from a database perspective. You can use the same database instance with multiple database schemas, each with a different user, or you can really use totally different databases.

The hard part of this would be the web hosting for Redmine. If you only have one server, then you need to create a separate virtual host or port for each. Otherwise, you can use a separate domain and server for each one. It's up to you how you want to do it.

Redmine doesn't support what you're asking for, since the issue ID is a unique key, and all issues across projects share the same database table. If you want to try patching it, you would have to:
  • Create a new table (or column in the issue table) with the project-specific id
  • Make sure that value is incremented by one for the project whenever you're creating a new issue
  • Replace anywhere the ID is displayed on the screen with the new project-issue-id
  • Change the routes so that edit and show issue URLs use the new ID rather than the traditional one
  • Fix query filters to use the id...

... dunno what else. I don't think it's worth even contemplating.