On 07.06.2013 21:54, Matevž Bradač wrote: > >> And another thing.. aren't we meant to have ticket numbers being used >> sequentially within each product? Would this break anything else? > The ticket id is an auto-incremented database key, so I don't think that > would work.
I thought we agreed a while ago that there are two ticket identifiers: the ticket-id, which is the same as in trac and the primary key of the ticket in the database; and the product-prefixed id, which is scoped within the product prefix and serves as an alias. The reason for doing is this way should be obvious -- a) you maintain immutability of existing ticket URLs after multiproduct upgrade, and b) when you import a new product (from, e.g., Jira; or, e.g., Subversion's issue tracker) you can keep the same product-prefixed IDs regardless of the ticket-id primary key gets assigned to the database record. This is a very important property of ticket IDs, IMNSHO. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. [email protected]
