Why mutli-project shares the issues' "Serial number"

Added by Jiongliang Zhang over 13 years ago

Question 1. why share the "Serial number" between all projects?

example, two projects: proj_a, proj_b:
  • in proj_a: create the first issue belongs to proj_a, the issue's "Serial number" is #1
  • in proj_b: create the first issue belongs to proj_b, the issue's "Serial number" isn't #1, it's #2.

Question 2.

  • when delete the last issue, like #3, then I create a new one, the "Serial number" becomes to #4, why not #3? I think #3 should be the correct for our projects.

Replies (5)

RE: Why mutli-project shares the issues' "Serial number" - Added by Mats Klepsland over 13 years ago

jiongliang zhang wrote:

Question 1. why share the "Serial number" between all projects?

example, two projects: proj_a, proj_b:
  • in proj_a: create the first issue belongs to proj_a, the issue's "Serial number" is #1
  • in proj_b: create the first issue belongs to proj_b, the issue's "Serial number" isn't #1, it's #2.

The only answer I can think of is to have a "unique" identifier for all the issues. This could be useful if the issues are registered in other systems like bug tracking systems or similar.

RE: Why mutli-project shares the issues' "Serial number" - Added by Gabriel Malkas over 13 years ago

There is only one table for issues, with an unique 'id' field. It is necessary to have an unique id in order to get the correct issue since the URLs are like /issues/show/xx. You cannot have the same id twice, it would be impossible to get the correct issue from that kind of URL.

RE: Why mutli-project shares the issues' "Serial number" - Added by Jiongliang Zhang over 13 years ago

why not add a table coloum to store the "Serial number" for every projects? Maybe this is another kind of function.

RE: Why mutli-project shares the issues' "Serial number" - Added by Isaiah DeRose-Wilson over 13 years ago

jiongliang zhang wrote:

why not add a table coloum to store the "Serial number" for every projects? Maybe this is another kind of function.

One big advantage of having global issue numbers is you can easily have related issues between different projects. For example issue #28 on project A could be related to issue #50 on project B and you wouldn't have any confusion because the projects would have globally unique issue numbers. This is a very handy feature when you start to manage a lot of related projects.

RE: Why mutli-project shares the issues' "Serial number" - Added by Gabriel Malkas over 13 years ago

Isaiah DeRose-Wilson wrote:

One big advantage of having global issue numbers is you can easily have related issues between different projects. For example issue #28 on project A could be related to issue #50 on project B and you wouldn't have any confusion because the projects would have globally unique issue numbers. This is a very handy feature when you start to manage a lot of related projects.

That's true, but wouldn't it be interesting to have an issue number like : "project_name_ID". I think JIRA does it this way. This is an example from the Zend Framework project (which uses Jira) : "ZF-7493"

(1-5/5)