Templates use plain HTML to define the layout and special fields that are replaced with actual field values when displayed or printed. For screen layouts, there are also special link formats that allow you to insert links to individual field editors. Templates have full access to User Defined Fields.
Maintenance of templates is carried out via the Tools / Options... / Templates menu option and is available only to Admin users. The built-in editor is used to modify template sections but, since it is not wysiwyg, you may find it easier to use an external editor and paste the results into the built-in editor.
There are three types of template:
Screen
This type of template allows you to define the layout of the visual elements of the pages displayed in the Detail Pane of the main screen. This template type is subdivided into separate sections representing the individual tabs:
| · | Bug Report
|
| · | Feature Request
|
| · | Enhancements
|
| · | Tasks
|
| · | Work Requests
|
| · | Notes (used for all notes fields)
|
| · | Images
|
| · | No Images (when no images are associated)
|
| · | History
|
| Header
|
| Odd
|
| Even
|
| Footer
|
| · | Criteria (for Queries)
|
As well as allowing %fieldname% keywords which are expanded to the actual value of the field at runtime, screen templates allow links to be inserted to the built-in field editors. These links take the form:
| <a href="FieldEdit:FieldName,%25id%25">DisplayText</a>
|
where FieldName is the name of the field, DisplayText is what the user sees, and %25id%25 is replaced with the current Issue ID. In the built-in Html editor, all the valid Links and Values are available from the toolbar and the context menu and the relevant Html will automatically be inserted for the relevant fields.
When a user clicks on one of these fields, the default editor for that field type is displayed to allow users to modify the value assigned to it.
Page Report
Page Report templates are similar to the Screen templates in that they are separated into similar sections:
| · | Header
|
| · | Bug Report
|
| · | Feature Request
|
| · | Enhancements
|
| · | Tasks
|
| · | Work Requests
|
| · | Notes (used for all notes fields)
|
| · | Attachments
|
| Header
|
| Odd
|
| Even
|
| Footer
|
| · | History
|
| Header
|
| Odd
|
| Even
|
| Footer
|
| · | Footer
|
Note that, with page reports, the Header section must start with the <body> tag and the Footer section must end with the </body> tag. The sections in between should not contain either of these tags.
Page Reports can use the <page> tag to force a new page when printing. This tag has no effect when displaying the report.
List Report
The List Report templates can be used to report on the fields common to Bug Reports and Feature Requests. For this reason they have the following section:
| · | Issue ( Bug/Feature )
|
| Header
|
| Odd
|
| Even
|
| Footer
|
Neither the Page Report or the List Report have access to the <a href links since they are designed for printed output or use outside TC Tracker.
© 1995-2011 Quality Software Components Ltd