Ozibug - web based bug tracking


Access control
Role based Access to the system is restricted by login, with access to various functionality controlled by the role to which a user is assigned. This includes read only access for guests, create and limited update access for customers full browsing and update access for developers, mass update access for managers and configuration only access for administrators.
Module based Access to the system is restricted by login, with access to modules controlled by the user id. This is configured by the administrator and can confine any user to any module.
Bug based Access to the system is restricted by login, with visibility and access of bugs controlled by the role to which a user is assigned, module access defined by the user id and the bug's privacy attribute. Guests and Customers cannot see private bugs entered by other Customers, Developers and Managers.
Comment based Access to the system is restricted by login, with visibility and access of comments for specific bugs controlled by the role to which a user is assigned, module access defined by the user id and the bug's privacy attribute. Guests and Customers cannot see private comments entered by other Customers, Developers and Managers.
Read only Access to the system is restricted by login, with the update ability of bugs controlled by the role to which a user is assigned and the bug's status and module type. Only Managers can update bugs with a read only status or module type.
Administration interface Administrators can configure system preferences, reference data, users and their access level, database connections and repositories, as well as view log files and system statistics.
Auditable All changes to bugs are audited, detailing when, who and what changes were made. Other significant events such as logins and logouts are also audited.
Authentication Ozibug can optionally be configured to support pluggable authentication modules, whereby user authentication is performed against an external source such as a user management system or LDAP directory.
Customizable While a working system is available out of the box, the system can (and would be expected to) be customized to meet project specific needs. For example, the colour scheme, system name, logos and bug identifier format can be changed to match corporate standards, reference data can be customized and expanded, and the data repositories can be relocated to a bigger or faster disk.
File attachments Files such as screen shots and log files can be uploaded and attached to a bug for subsequent viewing.
Forgotten password In the event of a forgotten password a temporary password can be requested by a user and sent to their registered email address.
Incoming mail gateway Ozibug can be configured with an incoming mail gateway to enable the automatic creation of bugs from mail submitted to an external mail source. This can be used, for example, in a support or help desk situation where all problems are submitted via email and subsequently tracked in Ozibug.
Internationalized The Ozibug application is fully internationalized and capable of supporting multiple locales. This is achieved by plugging in locale specific resource bundles (language packs) containing html pages and messages. The resources used will be determined by the locale specified in the users web browser.
Linked bugs Create (or remove) links between related bugs in any accessible module. The linked bugs can be subsequently viewed in a single click.
Modules Modules are the core of Ozibug allowing bug or defect tracking at a module, product or project level. Multiple modules are supported, providing a single, centralized repository for all your tracking needs.
Multi-platform access Since all content is delivered in html, the system is accessible from any browser, on any platform, from anywhere, at any time. All that is needed for access is a web browser. This avoids all the headaches that come with deploying client applications to multiple platforms, or even just deploying client applications to a single platform!
Notification Users can be notified of changes to bugs via email. They can be notified of bugs that they have created, been assigned to (or from) or have registered an interest in. Templates can be used to customize the presentation and content of both the subject and body of the email. Additional notifications can be enabled to always notify a nominated user(s) of events such as creation of a new bug or closing of a bug.
Platform independent server The Ozibug application is written entirely in Java utilizing servlet technology. This enables the installation and running of Ozibug on any platform for which a Java Virtual Machine (JVM) and servlet container are available.
Reference data Ozibug is shipped with a default set of priority and status reference data that is adequate for getting a system up and running, however all values can be customized to support corporate naming conventions. Additional custom fields can be added on a per module basis to allow the tracking of module specific attributes.
Reports
Custom Users can carry out custom queries and generate adhoc reports on a single module or across multiple modules. Every field can be included in a report and most fields can be used to filter and sort the data. There are six different types of reports, namely plain text (summary and detail), XML (detail), CSV (detail), RSS (summary) and HTML (summary).
Release Notes Users can generate release notes from all bugs in a module based on a template. Templates can be customized to suit various presentation styles and can include any number of fields from each bug in the module.
RSS RSS documents (or feeds) can be generated from a custom report for integration into RSS aggregator tools such as Outlook Express, Netscape or Amphetadesk.
Searchable Searching and sorting on the bug database is provided to assist users in the prioritization, allocation and tracking of bugs. Multiple named filter and sort criteria can be saved and persist between logins. Quick sorting can be performed by a single click on a column heading.
Storage
XML By default all data (from configuration to bugs) is stored in the native file system using XML based repositories. This approach means no additional database is required to use the system.
Database The system can optionally be configured to store the data in any JDBC compliant database.
 
Back