Current Version: BugLogHQ 1.5.204

Download Now    or    Fork in GitHub

What's New in BugLogHQ 1.5.204

• Added two new rule types: "Discard" and "HeartbeatMonitor". Discard is used to tell buglog to discard and not process bug reports that match a given criteria. HeartbeatMonitor can be configured to send an email alert if a message matching a given criteria has not been received in the last X minutes.
• Added two more lifecycle execution points for rules: "processQueueStart" and "processQueueEnd"; these methods execute before the queue processing begins and when it ends respectively and regardless of if there are items on the queue or not.
• Rule processor now also reports errors to the current buglog instance instead of only writing to a log file.
• BugLog now uses BugLog to track itself (duh, finally!)

What's New in BugLogHQ 1.5

• Extensions are now stored on a database instead of an XML file
• Creating a rule instance is now much more user friendly because application, host and severity codes can be selected via dropdowns; or can also be prepopulated from an existing bug report.
• Added support for defining settings for multiple environments (dev,qa,prod1,prod2,etc). Once the environment is detected buglog can override any setting with custom values.
• Added option to disable editing settings through the UI (useful if you have your config file versioned and only want to configure buglog that way)
• Added the "BugLog Digest" which is a configurable and periodic email summary of all reports received in the last X hours.
• Rewrote the "iphone" UI to be for mobiles in general (now its accessible at /bugLog/mobile), also there is an improved platform detection when going to /bugLog. If you go with any mobile browser you should get redirected to the new UI, otherwise you go to the regular desktop UI
• Multiple bug fixes

What's New in BugLogHQ 1.4

• Asynchronous processing of BugReports and Rules (Increases application's response and scalability)
• Simplified application configuration via a new "Settings" screen
• User management. Users can be divided now in two roles: regular users (with limited control) and administrators
• Optional JIRA integration. Create JIRA issues directly from BugLogHQ
• Change password screen (no more editing table directly to do this)
• Optionally require an API Key from applications to submit bug reports to BugLog.
• Enable/Disable rules as you need them.
• New rule type "FirstMessageAlert". Be alerted via email only the first time each distinct message arrives.
• Ability to "purge" history and delete all bug reports older than X number of days.