## This file is subject to the terms and conditions defined in
## file 'LICENSE', which is part of this source code package.
## Copyright (c) 2009 SKR Farms (P) LTD.
<%inherit file="/base/basic1.html"/>
<%namespace name="elements" file="/component/elements.html"/>
<%namespace name="forms" file="/component/forms.html"/>
<%!
page_tooltips = [
[ 'Ticket-list',
"""List of all tickets tracked under this project, organised in grid-style,
enabling users to edit ticket attributes in-line. To know how, just
double click on any of the grid's cell (that are not highlighted gray) and
edit it. It is also possible to navigate from one cell to another using
'up', 'down', 'left', 'right' arrows, to edit just press enter and edit. To save
the edited content, just press 'enter' or click outside the cell.
The header row in the grid can be used for two purpose. One, to sort the list
by desired column (by left clicking), two, to add/remove columns (by right
clicking).
"""
],
[ 'Standard-filters',
"""Standard ticket filters are named filter rules, based on complex regular
expressions defined at the backend. First among the list of standard filters
will be interpreted as default filter. These filters are available for all
registered users. Contact site-administrator to define a new type of standard
filter.
"""
],
[ 'Custom-filters',
"""Listed tickets can further be filtered using its attribute values, like,
type, severity, status, owner, component, milestone and version. When multiple
values are selected, filter rules will be ANDed.
"""
],
[ 'Saved-filters',
"""Custom filters can be saved under the user who is defining the
filter.
"""
],
[ 'Ticket',
"""Track issues, bugs, features, tasks etc ... using tickets.
The three main attributes of a ticket are type, status, severity.
Type should give an idea about why? and what? of a ticket. Status
tracks ticket workflow. Severity tells how severe the ticket is to the
project (synonymous to priority).
Users can move tickets from one status to another, also setting
its due-date. User who is changing the ticket status will become the new
owner of the ticket.
If, in case a ticket expects a response from a user other than the ticket's
owner, it can be indicated so using 'promptuser' attribute.
Use ticket id, where ever the ticket needs to be referenced.
"""
],
[ 'Attachments',
"""Add summary and tags to ticket attachments."""
],
[ 'Timeline',
"""Timeline of ticket(s) activity"""
],
]
%>
<%def name="hd_links()">
${parent.hd_links()}
%def>
<%def name="hd_script()">
${parent.hd_script()}
%def>
<%def name="ticketindex( typenames, severitynames, statusnames, users,
components, milestones, versions )">