Edgewall Software

Changes between Version 3 and Version 4 of TicketAliases


Ignore:
Timestamp:
Jan 23, 2016, 1:57:36 PM (8 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TicketAliases

    v3 v4  
    1 #REDIRECT ticket:976
     1[[PageOutline(2-5,Contents,pullout)]]
    22
    3 In the meantime, this is the:
     3= Ticket Aliases Proposal
    44
    5 = Ticket Aliases Proposal =
     5== Introduction
    66
    7 Tickets are identified by a number.
    8 That's fine, except that it sometimes happen that one has to work
    9 simultaneously on several dozens of tickets.
    10 In that case, knowing them by heart can become problematic...
     7Tickets are identified by a number. It can happen that one has to work simultaneously on many tickets, and knowing them by heart can become problematic.
    118
    12 Of course, there's the Report, Query and Search facilities.
    13 One could even use the Wiki to maintain informal groups of tickets.
     9Of course, there's the Report, Query and Search facilities to identify them and keep track of them. One could even use the Wiki to maintain informal groups of tickets.
    1410
    15 But it would be nice to have textual aliases for tickets.
    16 The alias would be an alternative identifier for the ticket.
     11But it would be nice to have textual aliases for tickets. The alias would be an alternative identifier for the ticket.
    1712
    18 There would be a very simple way to achieve this: simply create a wiki page
    19 having the desired alias name, and put the appropriate ticket TracLinks
    20 as its only content!
     13There 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!
    2114
    22 Then, before displaying the page, the Wiki module could check
    23 quite simply if the only content of the page is a link,
    24 and if this is the case, simply redirect to the corresponding target.
     15Then, 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.
    2516
    26 == Extension to other Trac objects ==
     17See also #976.
    2718
    28 As one can see, this mechanism would work not only tickets,
    29 but for any kind of Trac object (aliases to wiki pages, changesets,
    30 file, etc.)
     19== Extension to other Trac objects
    3120
    32 This mechanism can be implemented in a similar way than the ''redirect''
    33 feature of other Wikis:
    34  * http://en.wikipedia.org/wiki/Redirect_page and [http://meta.wikimedia.org/wiki/Help:Redirect WikiMedia's #REDIRECT]
    35  * [http://moinmoin.wikiwikiweb.de/HelpOnProcessingInstructions?highlight=%28redirect%29 MoinMoin's #redirect]
    36  * A [http://svn.ipd.uni-karlsruhe.de/trac/javaparty/wiki/TracRedirect redirect] macro for Trac,
    37    which could be used as a starting point for the implementation.
    38    I think it would actually be better if Trac had this capability built-in:
    39    * easier installation (i.e. no installation)
     21This mechanism would work not only tickets, but can be used for any kind of Trac object, such as aliases to wiki pages, changesets,
     22file, etc.
     23
     24This mechanism can be implemented in a similar way to the ''redirect'' feature of other Wikis:
     25 * Wikipedia's [wikipedia:Redirect_page] and !WikiMedia's [http://meta.wikimedia.org/wiki/Help:Redirect #REDIRECT].
     26 * MoinMoin's [http://moinmoin.wikiwikiweb.de/HelpOnProcessingInstructions?highlight=%28redirect%29 #redirect].
     27 * A [http://svn.ipd.uni-karlsruhe.de/trac/javaparty/wiki/TracRedirect redirect] macro for Trac, which could be used as a starting point for the implementation. It would be even better if Trac had this capability built-in:
     28   * no installation steps required
    4029   * combine this with a TracAdmin `wiki rename` command (see #1106)