Bug, issue Tracking
Bug tracking is the process you use to address programming errors found. This process includes recording the bug, reviewing it, recording the fix needed, and deciding whether or not the bug will be fixed considering budget and schedule. Keeping good records of decisions made will help to control the scope of the project. Bug tracking also enables you to know what was done with identified issues, why the system was changed, and what future changes to consider.
From : www.epri.com/eprisoftware/processguide/glossary.html
IssueView
Features:
Hierarchical Projects - You can track Issues in multiple, dissimilar, projects. Each project can define a name for the items it tracks (e.g., You can track Bugs, Sales Leads, Tasks, etc.). Projects are organized in a hierarchical tree structure.
User Defined Fields - Each project is based on a Template, which determines the fields in the project. All projects based on a template share a common set of Fields. Ten field types are available: CheckBox, Choice, ComboBox, Contacts, Date, Number, String, Text Tab, and Text Tab Secure, URL. These fields can be arranged in any one of 6 window layouts, with a graphical, drag and drop editor.
Advanced Issues Grid - You can edit in place, drag and drop issues, and group rows by one or more columns. Multiple issues can be updated at once.
Preview Pane - You can display basic information about the selected issue in a preview pane located below the Issues Grid.
E-Mail Integration - E-Mail notifications are sent when an issue changes. You can also select issues, export them to .html, launch your default e-mail client, with the html formatted issues as part of the content - all with a single right-click of the mouse.
Filters - You can create Public and Private filters for viewing a subset of the Issues in a Project.
Search - You can search for Issues based on text in the Abstract and/or a Text Tab fields.
Sorting - You can specify a sort order when defining a Filter, or by Clicking on a column header in the Issues Grid.
Contacts - There is a database for storing Contact information for Users, Clients, Prospects, etc.
Security - Access to IssueView requires a User ID. An administrator can assign specific permissions to a User ID - limiting the actions that user can perform.
Limit Users to Specific Projects - You can grant users access to a limited subset of projects, and assign them different permissions in each project.
Issue History - The history of changes to each Issue is tracked, and can be displayed.
Attachments - Files can be attached to Issues. An attachment can be created by pasting text, graphics, or files from the Windows Clipboard. Graphics attachments (png, bmp, jpg and gif files) can be viewed in an Issue Manger window; all other attachments are opened via the Windows Explorer. Attachments are stored in the database. Screen Captures are stored in an extremely compressed format.
Context Sensitive Help - Help is available in most dialogs.
Reporting - Issues can be printed in a variety of reports. The built-in reporting tool enables you to select the information to be included, and specify basic formatting options.
Data Export - Issues can be exported in a variety of formats that can be imported into Spreadsheets, Databases, and Word Processors.
Customization - In addition to the ability to specify Template Defined Fields (which allows you to specify the Fields, their names and data types for each Project) each user can:
Select which Fields are displayed in the Issues Grid for each project;
Specify default values for new Issues for each project;
Select a default Startup Project;
Select a default initial filter for each project;
Specify a default sort order (by ID, Ascending or Descending);
Customize the Grid display (e.g., Grid Lines, Row Selectors, Row Numbers, etc.)
visit
IssueView
IssueView was visited : 153 times
Loading .....