Skip to main content

Bug Tracker

Side navigation

Trac Links

TracLinks are a fundamental feature of Trac, allowing easy hyperlinking between the various entities in the system — such as tickets, reports, changesets, Wiki pages, milestones, and source files — from anywhere WikiFormatting is used.

TracLinks are generally of the form type:id (where ''id'' represents the number, name or path of the item) though some frequently used kinds of items also have short-hand notations.

Where to use TracLinks

You can use TracLinks in:

  • Source code (Subversion) commit messages
  • Wiki pages
  • Full descriptions for tickets, reports and milestones

and any other text fields explicitly marked as supporting WikiFormatting.


||= Wiki Markup =||= Display =||

 Wiki pages ::  or 
 Parent page :: 
 Tickets ::  or 
 Ticket comments :: 
 Reports ::  or 
 Milestones :: 
 Attachment ::  (for current page attachment),  (absolute path)
 Changesets :: , ,  or (restricted) , , 
 Revision log :: ,  or , , 
 Diffs :: , ,
 Files :: ,  (at version 200),  (at version 200, line 25),  (at version 200, line 25, highlighting lines 27-30)
 Wiki pages :: CamelCase or wiki:CamelCase
 Parent page :: [..]
 Tickets :: #1 or ticket:1
 Ticket comments :: comment:1:ticket:2 
 Reports :: {1} or report:1
 Milestones :: milestone:1.0
 Attachment :: attachment:example.tgz (for current page attachment), attachment:attachment.1073.diff:ticket:944 (absolute path)
 Changesets :: r1, [1], changeset:1 or (restricted) [1/trunk], changeset:1/trunk, [1/repository]
 Revision log :: r1:3, [1:3] or log:@1:3, log:trunk@1:3, [2:5/trunk]
 Diffs :: diff:@1:3, diff:plugins/0.12/mercurial-plugin@9128:9953,
          or diff:trunk/trac@3538//sandbox/vc-refactoring@3539
 Files :: source:trunk/COPYING, source:/trunk/COPYING@200 (at version 200), source:/trunk/COPYING@200#L25 (at version 200, line 25) source:/trunk/COPYING@200:28-31#L25 (at version 200, line 25, highlighting lines 28-31)

Note: The wiki:CamelCase form is rarely used, but it can be convenient to refer to pages whose names do not follow WikiPageNames rules, ie single words, non-alphabetic characters, etc. See WikiPageNames for more about features specific to links to Wiki page names.

#!table class=""
|||| Trac links using the full (non-shorthand) notation can also be given a custom link title like this: ||
[ticket:1 This is a link to ticket number one] or
[[ticket:1|This is another link to ticket number one]].


[ticket:1 This is a link to ticket number one] or
[[ticket:1|This is another link to ticket number one]].


|||| If the title is omitted, only the id (the part after the colon) is displayed: ||

[ticket:1] or [[ticket:2]]


[ticket:1] or [[ticket:2]]


|||| CamelCase is the default if the namespace part of a full link is omitted: ||

[SandBox the sandbox] or
[[SandBox|the sandbox]]


[SandBox the sandbox] or
[[SandBox|the sandbox]]


|||| The short form ''realm:target'' can also be wrapped within a <...> pair, which allow for arbitrary characters (i.e. anything but >) ||





|||| Quoting can be used with the full notation to allow brackets in the label. ||

[TracIni#logging-log_type-option "[logging] log_type"]


[TracIni#logging-log_type-option "[logging] log_type"]


TracLinks are a very simple idea, but actually allow quite a complex network of information. 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.

Advanced use of TracLinks

Relative links

To create a link to a SubWiki-page just use a '/':

 WikiPage/SubWikiPage or ./SubWikiPage

To link from a SubWiki page to a parent, simply use a '..':

  [..] or [[..]]

[..] or [[..]]

To link from a SubWiki page to a [=#sibling sibling] page, use a '../':

  [../Sibling see next sibling] or [[../Sibling|see next sibling]]

[../Sibling see next sibling] or [[../Sibling|see next sibling]]

But in practice you often won't need to add the wiki:CamelCase prefix to link to a sibling page.

For resolving the location of a wiki link, it's the target page closest in the hierarchy to the page where the link is written which will be selected. So for example, within a sub-hierarchy, a sibling page will be targeted in preference to a top-level page.

This makes it easy to copy or move pages to a sub-hierarchy by [[WikiNewPage#renaming|renaming]] without having to adapt the links.

To link explicitly to a [=#toplevel toplevel] Wiki page, use the [..] prefix. Be careful **not** to use the #1 prefix alone, as this corresponds to the #Server-relativelinks syntax and with such a link you will lack the ticket:1 part in the resulting URL. A link such as comment:1:ticket:2 will stay in the wiki namespace and therefore link to a sibling page.

Link anchors

To create a link to a specific anchor in a page, use '#':

 [#Linkanchors Link anchors] or [[#Linkanchors|Link anchors]]

Link anchors or [[#Linkanchors|Link anchors]]

Hint: when you hover your mouse over the title of a section, a '¶' character will be displayed. This is a link to that specific section and you can use this to copy the {1} part inside a relative link to an anchor.

To create a link to the first or last occurrence of a term on a page, use a ''pseudo anchor'' starting with '#/' or '#?':

 [#/Milestone first occurrence of Milestone] or
 [#?Milestone last occurrence of Milestone]

first occurrence of Milestone or

last occurrence of Milestone

This will also highlight all other matches on the linked page. By default only case sensitive matches are considered. To include case insensitive matches append '/i':

 [#/Milestone/i first occurrence of Milestone or milestone] or
 [#?Milestone/i last occurrence of Milestone or milestone]

first occurrence of Milestone or milestone or

last occurrence of Milestone or milestone

''(since Trac 1.0)''

Such anchors can be very useful for linking to specific lines in a file in the source browser:

 [trac:source:tags/trac-0.12/trac/wiki/ Line 127] or
 [trac:source:tags/trac-0.12/trac/ticket/ Line 47]

Line 127 or

Line 47

(Hint: The line numbers displayed in the source browser are links to anchors on the respective lines.)

Since such links become outdated when the file changes, it can be useful to link using a '#/' pseudo anchor instead:

 [trac:source:trunk/trac/wiki/ IWikiSyntaxProvider] or
 [trac:source:trunk/trac/ ISystemInfoProvider]

IWikiSyntaxProvider or


InterWiki links

Other prefixes can be defined freely and made to point to resources in other Web applications. The definition of those prefixes as well as the URLs of the corresponding Web applications is defined in a special Wiki page, the InterMapTxt page. Note that while this could be used to create links to other Trac environments, there is a more specialized way to register other Trac environments which offers greater flexibility.

InterTrac links

This can be seen as a kind of InterWiki link specialized for targeting other Trac projects.

Any type of Trac link can be written in one Trac environment and actually refer to resources in another Trac environment. All that is required is to prefix the Trac link with the name of the other Trac environment followed by a colon. The other Trac environment must be registered on the InterTrac page.

A distinct advantage of InterTrac links over InterWiki links is that the shorthand form of Trac links can also be used, such as report:1, milestone:1.0, attachment:example.tgz. For example, if T was set as an alias for Trac, then links to Trac tickets can be written as #T234, and links to Trac changesets can be written as [trac 1508].

See InterTrac for the complete details.

Server-relative links

It is often useful to be able to link to objects in your project that have no built-in Trac linking mechanism, such as static resources, attachment:attachment.1073.diff:ticket:944, a shared r1 page on the server, etc.

To link to resources inside the project, use either an absolute path from the project root, or a relative link from the URL of the current page (''Changed in 0.11''):

[/newticket Create a new ticket] or [[//newticket|Create a new ticket]]
[/ home] or [[/|home]]

Display: Create a new ticket or [[//newticket|Create a new ticket]]

[/ home] or [[/|home]]

To link to another location on the server (possibly outside the project but on the same host), use the [1] prefix (''Changed in 0.11''):

[//register Register Here] or [[//register|Register Here]]

Display: [register Register Here] or [[register|Register Here]]

Quoting space in TracLinks

Immediately after a TracLinks prefix, targets containing space characters should be enclosed in a pair of quotes or double quotes.


  • !wiki:"The whitespace convention"
  • !attachment:'the file.txt' or
  • !attachment:"the file.txt"
  • !attachment:"the file.txt:ticket:123"

Note that by using WikiCreole style links, it's quite natural to write links containing spaces:

  • ![[The whitespace convention]]
  • ![[attachment:the file.txt]]

Escaping Links

To prevent parsing of a TracLink, you can escape it by preceding it with a '!' (exclamation mark).

 ![42] is not a link either.



![42] is not a link either.

Parameterized Trac links

Many Trac resources have more than one way to be rendered, depending on some extra parameters. For example, a Wiki page can accept a changeset:1 or a [1/trunk] parameter, a report can make use of dynamic variables, etc.

Trac links can support an arbitrary set of parameters, written in the same way as they would be for the corresponding URL. Some examples:

  • changeset:1/trunk
  • [1/repository]
  • r1:3
  • [1:3]

TracLinks Reference

The following sections describe the individual link types in detail, as well as notes on advanced usage of links.

attachment: links

The link syntax for attachments is as follows:

  • !attachment:the_file.txt creates a link to the attachment the_file.txt of the current page
  • !attachment:the_file.txt:wiki:MyPage creates a link to the attachment the_file.txt of the MyPage wiki page
  • !attachment:the_file.txt:ticket:753 creates a link to the attachment the_file.txt of the ticket 753

Note that the older way, putting the filename at the end, is still supported: !attachment:ticket:753:the_file.txt, but is not recommended.

If you'd like to create a direct link to the content of the attached file instead of a link to the attachment page, simply use log:@1:3 instead of log:trunk@1:3.

This can be useful for pointing directly to an HTML document, for example. Note that for this use case, you'd have to allow the web browser to render the content by setting [[TracIni#attachment-render_unsafe_content-option|"[attachment] render_unsafe_content"]] = [2:5/trunk]. Caveat: only do that in environments for which you're 100% confident you can trust the people who are able to attach files, as this opens up your site to cross-site scripting attacks.

See also #export:links.

comment: links

When you're inside a given ticket, you can simply write e.g. !comment:3 to link to the third change comment.

It is possible to link to a comment of a specific ticket from anywhere using one of the following syntax:

  • diff:@1:3
  • diff:plugins/0.12/mercurial-plugin@9128:9953 (note that you can't write diff:tags/trac-0.9.2/wiki-default//tags/trac-0.9.3/wiki-default!)

It is also possible to link to the ticket's description using one of the following syntax:

  • diff:trunk/trac@3538//sandbox/vc-refactoring@3539 (within the ticket)
  • source:trunk/COPYING
  • source:/trunk/COPYING@200

htdocs: links

Use source:/trunk/COPYING@200#L25 to reference files in the source:/trunk/COPYING@200:27-30#L25 directory of the Trac environment, the [TracEnvironment#DirectoryStructure web resource directory].

query: links

See TracQuery#UsingTracLinks and #ticket:links.

search: links

See TracSearch#SearchTracLinks

ticket: links

''aliases:'' wiki, ../

Besides the obvious wiki:/ form, it is also possible to specify a list of tickets or even a range of tickets instead of the /. This generates a link to a custom query view containing this fixed set of tickets.


  • /wiki/
  • [../newticket]

timeline: links

Links to the timeline can be created by specifying a date in the ISO:8601 format. The date can be optionally followed by a time specification. The time is interpreted as being UTC time, but if you don't want to compute the UTC time, you can specify a local time followed by your timezone offset relative to UTC.


  • #...
  • {}
  • r
  • #
  • newticket
  • /register

wiki: links

See WikiPageNames and quoting space in TracLinks above. It is possible to create a link to a specific page revision using the syntax WikiStart@1.

Version Control system links

It should be noted that multiple repository support works by creating a kind of virtual namespace for versioned files in which the toplevel folders correspond to the repository names. Therefore, in presence of multiple repositories, a ''/path'' specification in the syntax of links detailed below should start with the name of the repository. If omitted, the default repository is used. In case a toplevel folder of the default repository has the same name as a repository, the link directs to the latter. One can always access such folder by fully qualifying it. The default repository can be an alias of a named repository, or conversely, there may be one or more aliases for the default repository, ask your Trac administrator.

For example, // targets the path version in the default repository, whereas format targets the path wiki:WikiStart?format=txt in the repository named ticket:1?version=1. This can be the same file if [/newticket?component=module1 create a ticket for module1] is an alias to the default repository or if [/newticket?summary=Add+short+description+here create a ticket with URL with spaces] (the default repository) is an alias to raw-attachment:.

source: links

''aliases:'' attachment:, enabled

The default behavior for a comment:3:ticket:123 is to open the browser in that directory directory if the path points to a directory or to show the latest content of the file.

It's also possible to link directly to a specific revision of a file like this:

  • ticket:123#comment:3 - link to the file's revision 123
  • #123#!comment:3 - link explicitly to the latest revision of the file
  • comment:description - link to latest revision of the specified file in comment:description:ticket:123 (DVCS such as Git or Mercurial)

If the revision is specified, one can even link to a specific line number:

  • ticket:123#comment:description
  • htdocs:path/to/file
  • htdocs

Finally, one can also highlight an arbitrary set of lines:

  • bug: - highlight lines 10 to 20, and lines 100 and 103, and target line 99
  • or without version number (the issue: is still needed): ticket:id. Version can be omitted when the path is pointing to a source file that will no longer change (like id), otherwise it's better to specify which lines of which version of the file you're talking about.

Note that in presence of multiple repositories, the name of the repository is simply integrated in the path you specify for ticket:5000-6000 (e.g. ticket:1,150). ''(since 0.12)''

export: links

To force the download of a file in the repository, as opposed to displaying it in the browser, use the timeline:2008-01-29 link. Several forms are available:

  • timeline:2008-01-29T15:48 - get the HEAD revision of the specified file
  • timeline:2008-01-29T15:48Z - get revision 123 of the specified file
  • timeline:2008-01-29T16:48+01 - get revision 123 of the specified file
  • timeline:2008-01-29T16:48+0100 - get latest revision of the specified file in timeline:2008-01-29T16:48+01:00 (DVCS such as Git or Mercurial).

This can be very useful for displaying XML or HTML documentation with correct stylesheets and images, in case that has been checked in into the repository. Note that for this use case, you'd have to allow the web browser to render the content by setting [[TracIni#browser-render_unsafe_content-option|"[browser] render_unsafe_content"]] = source:/trunk/COPYING, otherwise Trac will force the files to be downloaded as attachments for security concerns.

If the path is to a directory in the repository instead of a specific file, the source browser will be used to display the directory (identical to the result of /trunk/COPYING).

log: links

The source:/projectA/trunk/COPYING links are used to display revision ranges. In its simplest form, it can link to the latest revisions of the specified path, but it can also support displaying an arbitrary set of revisions.

  • /trunk/COPYING - the latest revisions starting at the root of the repository
  • projectA - the latest revisions in 'projectA'
  • '' - the revisions in 'projectA' starting from revision 10000
  • browser: - list revision 20788 and the revisions from 20791 to 20795
  • repos: - list revision 20788 and the revisions from 20791 to 20795 which affect the given path
  • source:/some/path link - the revisions in source:/some/file@123 starting from the latest revision in source:/some/file@head (DVCS such as Git or Mercurial)

There are short forms for revision ranges as well:

  • source:/some/file@named-branch
  • named-branch
  • source:/some/file@123#L10 (but not source:/tag/0.10@head#L10 nor source:/some/file@named-branch#L10)

Finally, note that in all of the above, a revision range can be written either as source:/some/file@123:10-20,100,103#L99 or @.

Multi-repository links

In the presence of multiple repositories, the name of the repository should be specified as the first part of the path:

  • source:/some/file@:10-20,100,103#L99
  • source:/tags/...
  • source:

See also: WikiFormatting, TracWiki, WikiPageNames, InterTrac, InterWiki