Boards and statuses: customize your workflow
Learn how BugMojo boards, columns, and statuses work, then move bugs and shape a workflow that fits your team.
A board is where your bugs live after capture. It lays out every issue as a card in a column, so your team can see what is open, what is being fixed, and what is ready to test at a glance. Boards sit inside a project, and you can create more than one to match how your team actually works.
The status columns
Boards share one status pipeline so a bug means the same thing everywhere. The columns map to a bug's journey from report to fix:
- Open: a new bug that has been triaged but not started.
- In Progress: a developer is actively working on the fix.
- Dev Testing: the fix is written and being checked by the developer.
- QA Testing: QA is verifying the fix against the replay and repro steps.
- Closed: the bug is fixed and verified.
- Reopened: a closed bug came back and needs another look.
Move a bug across the board
Change a bug's status
Open the board. In the dashboard, choose your Company, then the Project, then the Board you want.
Find the bug. Scan the columns, or use search and filters to narrow the board down to the card you need.
Drag the card. Grab the bug's card and drop it into another column to change its status. BugMojo saves the change right away.
Or use the status menu. Open the bug, then pick a new value from the Status menu on the bug detail page. Use this when you are already reading the replay or logs.
Assign an owner. Set the Assignee to a teammate or an AI agent so it is clear who takes the bug forward from its new status.
Customize your workflow
You shape how your team works by how you set up and organize boards, not by inventing new statuses. A few moves cover most teams:
Tailor a board to your team
Create a board per workflow. Inside a project, add a separate board for each team, feature area, or release so unrelated bugs do not pile up together.
Sort with labels and priorities. Apply labels and set a priority from Critical down to None so the most urgent bugs rise to the top of each column.
Save the views you use most. Filter the board by status, assignee, priority, or label, then save it as a view your team can return to in one click.
Route work to agents. Assign a bug to an AI agent the same way you assign a teammate, so an agent can pick it up when it hits In Progress.
Common questions
What are the default bug statuses in BugMojo?
Every board uses the same status pipeline: Open, In Progress, Dev Testing, QA Testing, and Closed. A bug you reopen after it was closed moves to the Reopened status so the team knows it came back.
How do I move a bug to a new status?
Open the board and drag the bug's card to another column, or open the bug and pick a new status from the status menu. The change is saved instantly and shows up for everyone on the board.
Can I organize different teams or workflows separately?
Yes. Create a separate board for each team, feature, or release under a project. Each board shares the same statuses, and you tailor triage further with labels, priorities, and saved views.
Related articles
- Structure your workspace: companies, projects and boardsUnderstand how companies, projects and boards nest in BugMojo, and learn when to spin up a new project versus adding a board.
- Priorities and labels referenceUnderstand what each priority level means and how labels organize bugs, so your team triages a busy board consistently.
- Assign bugs to teammates or to AI agentsRoute any bug to the right owner (a teammate or an AI coding agent) from the same assignee control.
- Filter, search, and save viewsNarrow a busy board with filters and full-text search, then save the result as a view your team can reopen in one click.