A Web view is a Web application that provides a customized view of an Vector Issue Tracker project. A Web view can expose all the information stored in the project database, or just a subset of that information.
For example, employees who are not part of the help desk don't need to see all the issues in the project database, just the issues submitted by them. And they don't need to see any internal notes added to the issues by the help desk staff. Help desk staff, on the other hand, need access to all the issue information in the project database.
The tutorial shows you how to create a Web view that includes all the information in the project.
Normal views allow users to submit and update issues.
Read-only views allow users to review existing issues, but not to edit them. Users cannot submit new issues.
Submit-only views allow an unlimited number of users to submit issues to Issue Tracker projects from their Web browsers. Submit-only web views can include all fields or just the fields needed to submit a new issue.
Each Web view of a project can expose some, or all, of the available fields.
Related fields are grouped into "tabs". In a Web view, tabs are hyperlinks that allow users to automatically scroll down the page to a set of related fields.
For each of the tabs, decide which fields you want to export. If none of the fields on a tab are exported, the tab will not appear in the Web view.
In the shortcut bar, click Fields .
In the Tab list, click a tab to display the fields available for that tab.
In the Available list, click a field.
Click the button.
In the Tab list, click a tab to display the fields available for that tab.
Click the button.
To reorder the fields in the Export to View list, |
![]() ![]() |
The order of the fields in the list determines their layout in the Web view.
![]() |
||||||||||||||||||||||||
|
Fields are arranged in rows on a tab, generally with two fields per row (so that each row has two columns). Fields are laid out row-by-row in the order they are listed in the Export to View list.
You can force a field to span both columns by setting its Column Span attribute to 2. For a text box like Summary, you would also set the CSS Class to MemoFieldWidth and change the width (in characters of the field) so that the field uses the extra space.
By default, memo fields like Description span both columns.
Queries allow users to extract issues from the project database and display them in the Summary List. By exporting queries, you control which issues are visible in the view. For example, an employee view might include only a query such as "My Issues", so that employees can see only the issues they submitted.
In the shortcut bar, click Queries .
In the Available list, click a query and then click the button.
Click the button.
![]() | |||||||||
A. |
List of queries defined in the project. | ||||||||
B. |
| ||||||||
C. | Lists the queries exported to the Web view. |
![]() |
Generates the Web view. When you generate a Web view, the current settings in the Web View Editor are automatically saved, so that the next time you edit the view the same settings are reloaded. |
![]() |
Saves the settings for the Web view. Does not generate the Web view. |
Cancel |
Cancels all changes made since the last time you saved or generated the Web view. |