close
Warning:
Failed to sync with repository "ogBrowser-Git": (1366, "Incorrect string value: '\\xF0\\x9F\\x93\\xA6 I...' for column 'message' at row 1"); repository information may be out of date. Look in the Trac log for more information including mitigation strategies.
- Timestamp:
-
Mar 15, 2010, 9:46:23 AM (16 years ago)
- Author:
-
trac
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
v1
|
v2
|
|
| 17 | 17 | ''This will make the query module the default handler for the “View Tickets” navigation item. We encourage you to try this configuration and report back what kind of features of reports you are missing, if any.'' |
| 18 | 18 | |
| 19 | | '''''You will almost definitely need to restart your httpd at this point.''''' |
| 20 | 19 | |
| 21 | 20 | A report consists of these basic parts: |
| … |
… |
|
| 43 | 42 | }}} |
| 44 | 43 | Keep in mind that the integrity has to be maintained (i.e., ID has to be unique, and you don't want to exceed the max, since that's managed by SQLite someplace). |
| | 44 | |
| | 45 | You may also need to update or remove the report number stored in the report or query. |
| 45 | 46 | |
| 46 | 47 | == Navigating Tickets == |
| … |
… |
|
| 166 | 167 | === Automatically formatted columns === |
| 167 | 168 | * '''ticket''' -- Ticket ID number. Becomes a hyperlink to that ticket. |
| | 169 | * '''id''' -- same as '''ticket''' above when '''realm''' is not set |
| | 170 | * '''realm''' -- together with '''id''', can be used to create links to other resources than tickets (e.g. a realm of ''wiki'' and an ''id'' to a page name will create a link to that wiki page) |
| 168 | 171 | * '''created, modified, date, time''' -- Format cell as a date and/or time. |
| 169 | | |
| 170 | 172 | * '''description''' -- Ticket description field, parsed through the wiki engine. |
| 171 | 173 | |
| … |
… |
|
| 174 | 176 | SELECT id as ticket, created, status, summary FROM ticket |
| 175 | 177 | }}} |
| | 178 | |
| | 179 | Those columns can also be defined but marked as hidden, see [#column-syntax below]. |
| 176 | 180 | |
| 177 | 181 | === Custom formatting columns === |
| … |
… |
|
| 208 | 212 | numeric representation from the ''enum'' table. |
| 209 | 213 | |
| 210 | | === Changing layout of report rows === |
| | 214 | === Changing layout of report rows === #column-syntax |
| 211 | 215 | By default, all columns on each row are display on a single row in the HTML |
| 212 | 216 | report, possibly formatted according to the descriptions above. However, it's |
| … |
… |
|
| 218 | 222 | |
| 219 | 223 | * '''`_column`''' -- ''Hide data''. Prepending an underscore ('_') to a column name instructs Trac to hide the contents from the HTML output. This is useful for information to be visible only if downloaded in other formats (like CSV or RSS/XML). |
| | 224 | This can be used to hide any kind of column, even important ones required for identifying the resource, e.g. `id as _id` will hide the '''Id''' column but the link to the ticket will be present. |
| 220 | 225 | |
| 221 | 226 | '''Example:''' ''List active tickets, grouped by milestone, colored by priority, with description and multi-line layout'' |
