Switch from numeric issue ids to symbolic ones
Switches issue ids from #1 to something like MYID-1
#2 Updated by bajs bajs over 13 years ago
That would break urls pointing to the old project if the issue
is moved to another project, wouldn't it?
Issues should have the same id even if they are moved. I see
no reason to have project-specific IDs.
Having a "print name" for ids could work though, so
that issue 123 is written as "PROJ-123" everywhere
it's written. But it should still have the same proper handle
IMO, and any inputting of IDs should then accept both 123 and
PROJ-123. But I wouldn't ever use it because...
Another issue with project-local ID numbers is that you can't
ever ever change the prefix. If your customer communication,
version control commits, wiki and everything else refers to issue
"FoodProj-123", then you can't really change FoodProjs
name to EatProj.
I wouldn't use the PROJ-prefix at all, but you go right ahead.
But please don't break globally unique issue IDs. That would
break so many things for so many potential users.
#3 Updated by Ted Wise almost 14 years ago
Yes, it's a very simplistic patch - basically it's just for
show. It displays issue id's as <CODE>-<ID>, e.g.,
but nothing else changes. For example, the url to access
the issue is still /issue/show/45.
To do this correctly, you really want to make the display
efficient, switch each project to have it's own id numbers
(instead of having id's shared across all projects), and use
code ids on the inbound, e.g., /issue/show/proj-45.