Bugsink 1.4 Release

Bugsink 1.4 is here! The biggest addition? Tag-based search—a structured way to find both issues and individual events.

Introducing Tag-Based Search

Search in Bugsink is built entirely on tags (both user-supplied and derived from event properties). This means:

• Fast, structured filtering – A simple query language using key:value pairs.
• Works across issues and events – Find relevant data without sifting manually.
• Efficient, built-in implementation – Runs directly in the database for speed and simplicity.

To support this, Bugsink now provides per-issue tag overviews and a dedicated tag breakdown page for quick insights.

Already using Bugsink? Tags for past events aren’t retroactively computed on upgrade (to avoid slow migrations). You can either let new events accumulate tags automatically or run init_tags to generate tags for existing data.

For more details, read Introducing Search in Bugsink.

Further Features & Fixes

Beyond search, Bugsink 1.4 includes various improvements:

• Experimental PostgreSQL support – Bugsink’s test suite now runs against PostgreSQL. Running the Docker image with PostgreSQL is now possible, though not yet extensively tested (#21).
• Better handling of top-level message strings (#55).
• More robust createsuperuser behavior – Avoids running automatically when any users already exist (#54).
• MySQL compatibility fix – Adjusted Issue.calculated_* field lengths for better support.
• Additional event details – Logentry details now include level.

Upgrading to Bugsink 1.4

Bugsink 1.4 is available now. Give it a try and let us know how it works for you!

See the full changelog on GitHub.

Upgrade now or install Bugsink for the first time.