Feature #6884
IssueID by Project
| Status: | Closed | Start date: | 2010-11-13 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Issues | |||
| Target version: | - | |||
| Resolution: | Duplicate |
Description
I think it wuld be good or well it can be optional if you like to start on issue id 1 for all your projects,
Or just have it like it is today it fallow the next id that will comes up so it means fallowing.
If project 1 has 3 issue ids and you start a new project and make a new issue to it it got id 4
Related issues
History
#1
Updated by Jean-Philippe Lang about 12 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Another dup of #1926.
#2
Updated by SwedishMatch TimerWolf about 12 years ago
Jean-Philippe Lang wrote:
Another dup of #1926.
Can you tell why it won´t be fixed or implanted?
It culd be optional and can´t be hard to fix :/
#3
Updated by Jean-Philippe Lang about 12 years ago
SwedishMatch TimerWolf wrote:
Can you tell why it won´t be fixed or implanted?
See #282.
It culd be optional and can´t be hard to fix :/
I don't think it would be simple.
#4
Updated by SwedishMatch TimerWolf about 12 years ago
Why? It culd even use like the #282 example or why not diffrent tables or whatever
#5
Updated by Andriy Lesyuk over 8 years ago
Please check this solution. Note, that it requires you to specify the project key, which gets prepended to the issue number.