| 287 | | == [mainnav] [metanav] == |
| 288 | | The new [mainnav] and [metanav] can now be used to customize the text and link used for the navigation items, or even to disable them. |
| 289 | | |
| 290 | | In the following example, we rename the link to the Wiki start "Home", and hide the "Help/Guide". We also make the "View Tickets" entry link to a specific report . |
| 291 | | {{{ |
| 292 | | [mainnav] |
| 293 | | wiki.label = Home |
| 294 | | tickets.href = /report/24 |
| 295 | | |
| 296 | | [metanav] |
| 297 | | help = disabled |
| 298 | | }}} |
| | 306 | === [ticket-workflow] === #ticket-workflow-section |
| | 307 | ''(since 0.11)'' |
| | 308 | |
| | 309 | The workflow for tickets is controlled by plugins. |
| | 310 | By default, there's only a `ConfigurableTicketWorkflow` component in charge. |
| | 311 | That component allows the workflow to be configured via this section in the trac.ini file. |
| | 312 | See TracWorkflow for more details. |
| | 313 | |
| | 314 | === [milestone-groups] === #milestone-groups-section |
| | 315 | ''(since 0.11)'' |
| | 316 | |
| | 317 | As the workflow for tickets is now configurable, there can be many ticket states, |
| | 318 | and simply displaying closed tickets vs. all the others is maybe not appropriate |
| | 319 | in all cases. This section enables one to easily create ''groups'' of states |
| | 320 | that will be shown in different colors in the milestone progress bar. |
| | 321 | |
| | 322 | Example configuration (the default only has closed and active): |
| | 323 | {{{ |
| | 324 | closed = closed |
| | 325 | # sequence number in the progress bar |
| | 326 | closed.order = 0 |
| | 327 | # optional extra param for the query (two additional columns: created and modified and sort on created) |
| | 328 | closed.query_args = group=resolution,order=time,col=id,col=summary,col=owner,col=type,col=priority,col=component,col=severity,col=time,col=changetime |
| | 329 | # indicates groups that count for overall completion |
| | 330 | closed.overall_completion = truepercentage |
| | 331 | |
| | 332 | new = new |
| | 333 | new.order = 1 |
| | 334 | new.css_class = new |
| | 335 | new.label = new |
| | 336 | |
| | 337 | # one catch-all group is allowed |
| | 338 | active = * |
| | 339 | active.order = 2 |
| | 340 | # CSS class for this interval |
| | 341 | active.css_class = open |
| | 342 | # Displayed label for this group |
| | 343 | active.label = in progress |
| | 344 | }}} |
| | 345 | |
| | 346 | The definition consists in a comma-separated list of accepted status. |
| | 347 | Also, '*' means any status and could be used to associate all remaining |
| | 348 | states to one catch-all group. |
| | 349 | |
| | 350 | The CSS class can be one of: new (yellow), open (no color) or |
| | 351 | closed (green). New styles can easily be added using the following |
| | 352 | selector: `table.progress td.<class>` |
| | 353 | |
| | 354 | === [svn:externals] === #svn:externals-section |
| | 355 | ''(since 0.11)'' |
| | 356 | |
| | 357 | The TracBrowser for Subversion can interpret the `svn:externals` property of folders. |
| | 358 | By default, it only turns the URLs into links as Trac can't browse remote repositories. |
| | 359 | |
| | 360 | However, if you have another Trac instance (or an other repository browser like [http://www.viewvc.org/ ViewVC]) configured to browse the target repository, then you can instruct Trac which other repository browser to use for which external URL. |
| | 361 | |
| | 362 | This mapping is done in the `[svn:externals]` section of the TracIni |
| | 363 | |
| | 364 | Example: |
| | 365 | {{{ |
| | 366 | [svn:externals] |
| | 367 | 1 = svn://server/repos1 http://trac/proj1/browser/$path?rev=$rev |
| | 368 | 2 = svn://server/repos2 http://trac/proj2/browser/$path?rev=$rev |
| | 369 | 3 = http://theirserver.org/svn/eng-soft http://ourserver/viewvc/svn/$path/?pathrev=25914 |
| | 370 | 4 = svn://anotherserver.com/tools_repository http://ourserver/tracs/tools/browser/$path?rev=$rev |
| | 371 | }}} |
| | 372 | With the above, the `svn://anotherserver.com/tools_repository/tags/1.1/tools` external will be mapped to `http://ourserver/tracs/tools/browser/tags/1.1/tools?rev=` (and `rev` will be set to the appropriate revision number if the external additionally specifies a revision, see the [http://svnbook.red-bean.com/en/1.4/svn.advanced.externals.html SVN Book on externals] for more details). |
| | 373 | |
| | 374 | Note that the number used as a key in the above section is purely used as a place holder, as the URLs themselves can't be used as a key due to various limitations in the configuration file parser. |
| | 375 | |
| | 376 | Finally, the relative URLs introduced in [http://subversion.tigris.org/svn_1.5_releasenotes.html#externals Subversion 1.5] are not yet supported. |
| | 377 | |
| | 378 | == Discussion == |
| | 379 | |
| | 380 | ''Please discuss documentation changes here. Even better, send us documentation patches against the code, either on Trac-dev or on new tickets.'' |
| | 381 | |
| | 382 | * There is, apparently, an [svn] `repository_url` option that is not documented here. [[br]] |
| | 383 | No, there's no such thing. There ''might'' be a plugin providing support for this, for Trac 0.12. However, Trac 0.12 will support an `url` property for repositories. |
| | 384 | * It can be helpful to know the default values for each entry, perhaps specified in a common format such as square brackets [] at the end of the description (or at the beginning of the description). ''for 0.12?'' |
| | 385 | * Due to TracIni macros, there is no history of trac.ini settings changes between versions, and sometimes it is worthy to know when some some setting was removed. |
