🐛Triage and Workflow

Every error the widget captures lands on the project's Errors page, grouped so repeats of one bug are one row. How to read an error, turn it into a task or attach it to one, what happens when a fixed error comes back, and who hears about it.

Who hears about an assignment, a comment, or a status or property change on a task, how a burst of edits and a bulk action become one notification, and how the emails work.

Every way to get to the task you want: the board search and its highlighting, filtering by assignee, labels, priority or environment, and the ⌘K palette.

Add fields of your own to every task in a project — text, number, date, checkbox, URL, select, multi-select or team member — then filter the board by them and read them from your AI agent.

Rename, recolour, add and delete the priorities in your project — and what a rename means for the widget, your integrations and shared portal links.

How BugDump numbers tasks, what the project key in front of the number is for, which URLs open a task, and what changes if you rename a key.

Put the design file, the log, or the spec on the task itself — by button or by dropping it on the screen — and understand which files you can remove and which belong to the description.

A concrete daily routine for handling incoming reports, setting up board columns, and keeping a bug inbox from turning into a graveyard.

Turn on a public page at your-project.bugdump.com where people follow your tasks and upvote them, choose which tasks and how much of each report it shows, and pick a slug that works as its address.

Group reports into tasks, move them across a kanban board you configure, and give reporters a public page to follow along.

What each section of a report contains, and how to work backwards from a user's complaint to the line of code that caused it.