April is the month Bugspot turned into a tool a team shares: entries that link to each other, threaded comments, assignees, and a full activity log all landed. March built the spine — the entry, workflows, sign-in — and April is where the work started connecting to other work, and to the people doing it.
Entries that connect
Real work isn’t a flat list — things block other things, duplicate each other, or are just related. Bugspot now models that directly with entry relationships: an entry can have a parent, and can block, duplicate, or relate to others. A linked-entries panel on the detail view shows those connections in one place, so the web of dependencies around a piece of work is visible instead of living in someone’s head.
Talk it through
Entries now have threaded comments — reply to a specific point, keep sub-threads readable, and edit within a short window after posting. It’s the difference between an entry being a static form and being where the discussion actually happens.
Who’s on it
Work needs an owner. This month brought assignees end to end: assign an entry, see the assignee’s avatar right in the list, change it from a dropdown on the detail panel, and filter the list down to just what’s assigned to someone. The CLI can assign too — by username or email.
Behind that, Bugspot filled out how it handles people: a members area with invite, deactivation, and search, and a teams feature with its own settings and a user picker for adding people quickly. The groundwork for “who’s on this team, and who’s working on what.”
Sort, group, and save
As lists get longer, organizing them matters more than filtering them. The entries list gained sorting (click a column, flip the direction) and group-by, so you can slice a project by status, assignee, priority, or type and see it in buckets instead of one long scroll. And once you’ve built a view you like — filters, sort, and grouping together — you can keep it as a saved filter and come back to it in a click.
A record of what happened
Every entry now keeps an activity log — status changes, field edits, assignments — on its own tab. When you pick up a bug someone else has been working, you can see how it got to where it is instead of guessing.
Never lose your place
The list quietly tracks read state: entries you haven’t seen yet, and ones that changed since you last looked, are marked so your eye goes straight to what’s new. Small, but it’s the feature you miss immediately when a tracker doesn’t have it.
And in the terminal
The bugspot CLI kept pace: it can now create entries, fetch a single entry by key, list your configured attributes, and assign work — so more of the day-to-day never has to leave the shell.
That’s April. Between the relationships, the comments, the assignees, and the activity log, Bugspot stopped being a place to store work and became a place to do it together. Next up: milestones, live updates, and a much bigger CLI — but that’s the next post.
Bugspot is in public beta — start a project and put a team on it.