Project-specific ticket prefixes and numbering
|Reported by:||Owned by:|
With the addition of multiple projects in one Trac instance, it could be helpful to assign ticket identifiers with project-specific prefixes and independent numbering. The prefix would be configured wherever the project is configured. (trac.ini?) This would help differentiate tickets when referring to them by identifier. This is how JIRA assigns ticket identifiers.
For example, in a Trac with two project named Database (DATA) and Web Service (WS), the ticket references would look like:
With the next Database ticket being assigned DATA-103 and the next Web Service ticket being assigned WS-94. Since changing the way tickets are identified would probably be a huge change, maybe assigned ticket aliases would be a simpler workaround to provide the same functionality? I'm not sure what the best way to use these identifiers as wiki links would be, but the idea is that something like the following could be used to create wiki links:
- WS:93 (this might be easiest since you can treat each project prefix as a TracLinks namespace?)
Of course, if the identifier is implemented as an alias then it could get confusing with the underlying numeric identifiers. WS:93 and #342 could point to the same ticket. This also raises the question of what happens if a ticket is moved between projects. I don't have an understanding of the amount of work involved for this type of change, so this is just a suggestion for consideration. I do think it would be very useful for scenarios with 10+ projects sharing a ticket database.