Release Notes¶

Changes in v1.1 (2010-02-08)¶

NEW: Standalone mode with locally registered users.
NEW: Send issue reports by email.
NEW: Change LogDigger Server’s home directory (for configuration and logs) using Java system property.
NEW: Options to filter out or hide content of some parameters when saving HTTP POST/GET data (e.g. password or viewstate).
Improved: Simplified setup process allows you to choose operating mode for your LogDigger Server instance (Tracker, Standalone and Open mode).
Improved: When user reports an issue but the external issue tracker returns an error (e.g. due to failed custom field validation), errors are recognized and passed to user.
Fixed: Support for complex JIRA configurations using customized issue type schemes.
Fixed: Annotation image editor compatibility issue on Linux.
Many small fixes and improvements.

Copy any database drivers .jar files that you installed.
On Windows make sure to uninstall LogDigger Server 1.0 before installing 1.1.
The LogDigger Server will automatically upgrade database created by previous versions. In any case, it’s highly advisable that you make a database backup before upgrading.

Change: When bug is reported, instruct the browser extension to make a screenshot only for the page viewport. This still can be customized changing Data Collecting Preferences.
Fixed: Compatibility issues with SQL Server

Fixed: User login issue to JIRA 3 when the JIRA page shows the full user name, rather than login ID. (#762)