> I interpreted your statement above as to have global ticket ID and > product-specific ticket ID for a single ticket. If that's the case, > IMHO it is another source of confusion to have URLs /ticket/123456789 > (<=global) and /ticket/products/pid/ticket/12 . I mean : > > - Ticket identity is ambiguous > - The user would have to remember two completely unrelated IDs Just want to add a use case to Olemis's list: There are Trac plugins that provide there own UI that exposes ticket IDs to user (e.g. MasterTicketPlugin) and access ticket table directly by passing ticket API. That would be quite strange for a user to see one ID in Bloodhound pages and another ID in a plugin pages for the same ticket.
Cheers, Andrej
