Issue/Merge Request ids incremented based on project
Created by: mikkyhouse
Issue, merge requests IDs are being shared across projects. Issue ID 1,2 belong to project 1 and when a new issue is created in project 2, it gets the ID 3. I think ids should be per project. Would be easy to track the total no of issues/merge requests per project.
Activity
Created by: dubcanada
One thing you could do is rather then get rid of the current id. Just have a non incrementing/non unique column with a project specific id (1++ each issue/what ever). And change the id that it gets to the id based on project id & issue id.
However just so we all know github just maps the issue to the project. For example this issue is not #560 (closed). It is actually #3680015 (which you can see via the HTML).
By Administrator on 2012-03-16T12:51:57 (imported from GitLab project)
By Administrator on 2012-03-16T12:51:57 (imported from GitLab)
Created by: cweagans
Actually, I really like that it works the way it does. In fact, I'd really love to see a shortcut implemented where you could just do example.com/issue/1234 and then be redirected to the appropriate issue URL for that issue id.
By Administrator on 2012-04-09T02:16:21 (imported from GitLab project)
By Administrator on 2012-04-09T02:16:21 (imported from GitLab)
Created by: KindDragon
@cweagans +1
By Administrator on 2012-08-06T16:50:45 (imported from GitLab project)
By Administrator on 2012-08-06T16:50:45 (imported from GitLab)
Created by: Bertg
Implementing a feature like this if fairly difficult to do it right, depending on the DB that's behind it; without it really fixing any problem. You are also changing the unique identifier (from human pov) of a issue from just a number to a projectname+number.
If you want to solve the issue where you want to know the total issues per project; this won't even solve it; as a deleted issue would still have incremented the counter. If you want to know the total amount of issues per project a simple count + where statement will be more useful.
Further more; this would be really difficult to migrate towards from existing installs.
@cweagans suggestion is more valuable; but could be handled by the routing revamp in ticket #1568.
I would suggest to close this ticket.
By Administrator on 2012-10-03T10:40:12 (imported from GitLab project)
By Administrator on 2012-10-03T10:40:12 (imported from GitLab)
