LogDigger Server 1.1 released

We are pleased to announce the official release of LogDigger Server 1.1. There are several long awaited improvements and fixes so let’s start…

Improved issue trackers integration

We’ve fixed quite severe issue affecting integration with JIRA installations having complex issue types schemes. If you were unable to get issue reporting form in LogDigger for your JIRA project, there are big chances that you’ve been affected by this issue.

Beside the above mentioned, one of the quite annoying issues with the LogDigger Server v1.0 was its inability to collect errors reported by the issue tracker and show them to user. Although LogDigger recognizes required issue reporting fields, it doesn’t know their meaning so validation on the issue tracker may fail. This has been fixed so now you should see an error in the LogDigger’s issue reporting form as it comes from the issue tracker.

We feel very confident with the current level of compatibility with supported issue trackers, especially with Atlassian JIRA. (We admin giving JIRA more attention but, at least so far,  JIRA’s user community was quite vibrant, providing us with a necesary feedback and, well… reporting bugs in LogDigger Server.)

Setup and Operating modes

Simplified setup process allows you to choose the operating mode for your LogDigger Server instance:

• The Tracker Mode is tied to an external issue tracker, reusing its users, access control and issue reporting configuration.
• The Standalone Mode allows you to register users (and enable self-registration) on your LogDigger Server. Combined with the new emailing feature, this mode allows you to submit bug reports to any issue tracker accepting reports via email.
• The Open Mode is a simple, open access mode suitable for single-user installations.

It’s also worth to mention that default LogDigger Server’s home directory (that defaults to ~/.logdigger) used for configuration files, logs, etc. now can be changed using Java system properties.

Sending issue reports by email

Connecting LogDigger Server with your outgoing (SMTP) mail server, for each project you can choose to send issue reports to one or more email addresses. Emails sent by LogDigger server contain the complete issue report with attached screenshot and server logs (where available).

Other changes

Among a number of small fixes and improvements in v1.1, here are some that we hope will make your use of LogDigger easier:

• Fixed an issue with annotation image editor on Linux,
• On the project page you can obtain ready to use logdigger.xml for your project.
• In administration pages you can see the full path of configuration and log files used by the LogDigger Server.
• LogDigger Server will warn you if it’s running on a low memory (as it may seriously affect performance).

Migrating from LogDigger Server 1.0

There are no special upgrade tasks that you need to do. The LogDigger Server will automatically upgrade database created by the previous version. Just in case, we highly recommend that you make a database backup before upgrading.

If you’re using LogDigger Server for Windows, make sure to uninstall LogDigger Server 1.0 before installing 1.1.

And yes… hoping that you’ve switched to an enterprise grade database already, don’t forget to copy and install database driver jar file.

We hope you’ll like this update. As always, feel free to contact us with any problem, question or comment you may have.