Opened 19 years ago
Last modified 8 years ago
#976 new enhancement
[ER] Textual aliases for Tickets (and for any other Trac object) — at Initial Version
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | lowest | Milestone: | next-major-releases |
| Component: | wiki system | Version: | 0.11.2 |
| Severity: | minor | Keywords: | page alias, redirect |
| Cc: | bfults+trac@…, kasper.souren+trac@…, felix.schwarz@…, yoav@…, Ryan J Ollos | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Tickets are identified by a number. That's fine, except that it sometimes happen that one has to work simultaneously on several dozens of tickets. In that case, knowing them by heart can become problematic…
Of course, there's the Report, Query and Search facilities. One could even use the Wiki to maintain informal groups of tickets.
But it would be nice to have textual aliases for tickets. The alias would be an alternative identifier for the ticket.
There would be a very simple way to achieve this: simply create a wiki page having the desired alias name, and put the appropriate ticket TracLinks as its only content!
Then, before displaying the page, the Wiki module could check quite simply if the only content of the page is a link, and if this is the case, simply redirect to the corresponding target.
As one can see, this mechanism would work not only for tickets, but for any kind of Trac object (aliases to wiki pages, changesets, file, etc.)
