| | 1 | = Trac Links = |
| | 2 | |
| | 3 | As you might have guessed, TracLinks are a very fundamental feature of Trac. |
| | 4 | |
| | 5 | They allow easy hyperlinking to files, changesets, bugs/issues and wiki pages from anywhere in the system where WikiFormatting is used. |
| | 6 | |
| | 7 | TracLinks can refer to tickets, reports and changesets by simply writing the |
| | 8 | ticket, report and changeset numbers in the following notation: |
| | 9 | {{{ |
| | 10 | * Ticket #1 |
| | 11 | * Report {1} |
| | 12 | * Changeset [1] |
| | 13 | * File svn:trunk/COPYING. |
| | 14 | }}} |
| | 15 | Display: |
| | 16 | * Ticket #1 |
| | 17 | * Report {1} |
| | 18 | * Changeset [1] |
| | 19 | * File svn:trunk/COPYING. |
| | 20 | |
| | 21 | It seems a simple enough concept at a glance, but actually allows quite a complex network of information. |
| | 22 | |
| | 23 | In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made. |
| | 24 | |
| | 25 | == Where to use TracLinks == |
| | 26 | You can use TracLinks in: |
| | 27 | |
| | 28 | * Wiki pages |
| | 29 | * Ticket descriptions |
| | 30 | * Source code (Subversion) commit messages |
| | 31 | |
| | 32 | See also: WikiFormatting |
| | 33 | |
