Labels, Assignees, and Filters
Last updated: October 2, 2026
Every issue in OverlayQA carries a status, a type, a severity, an assignee, and any number of labels. Labels are shared across your whole workspace, so the same label means the same thing in the dashboard, the Chrome extension, Team Review, shared reports, exports, and the MCP server. This guide covers how to label and assign issues, how to filter the Issues page down to what matters, and how to set aside issues you will not fix.
Add a Label to an Issue
- Open the issue in the dashboard, the extension sidebar, or the Team Review drawer and find the Labels control.
- Open the Labels picker. Its search box reads Search or create a label…; start typing to filter the workspace's existing labels.
- Pick a label to apply it, or type a new name and choose Create and apply (the menu also offers New label…) to create the label and put it on the issue in one step.
Labels are workspace-wide. Creating one while labelling an issue adds it to the library for every project and every teammate. Any editor can create and apply labels; renaming and deleting are reserved for workspace owners and admins (see Manage Labels below).
Tip: Keep the library small and specific. A handful of labels that describe how work moves (for example a release, a client, or a component) filters better than one label per symptom.
Assign an Issue
Every issue has an Assignee. New issues default to the person who filed them, so a capture is never orphaned; change it from the Assignee control on the issue, or clear it to Unassigned. Assignees carry into exports, so a Jira or Linear ticket arrives with the right owner, and teammates can filter the Issues page by assignee.
Filter the Issues Page
The dashboard Issues page filters are checkbox lists, so you can combine several values in one filter and several filters at once. The same filters appear in the extension sidebar and the Team Review drawer.
| Filter | What it does |
|---|---|
| Status | Rests on Active issues, which shows everything still open and hides finished issues. Switch to All statuses, or tick individual statuses (Open, In Progress, Resolved, Verified, Closed). Reset to active issues brings the default back. |
| Type and Severity | Narrow to one or more types or severities; the controls read All types and All severity until you tick something. |
| Labels | Show issues carrying any of the ticked labels. No labels finds the issues nobody has categorised yet. Defaults to All labels. |
| Assignee | Show issues owned by specific teammates, or Unassigned work. Defaults to All assignees. |
| Created by | Show issues filed by specific people. Defaults to All creators. |
Ignore Issues You Will Not Fix
Some findings are real but not worth fixing: a third-party widget you cannot change, or a known trade-off. Choose Ignore from the issue's row menu to take it out of the active view without deleting it. Ignored issues keep their screenshot, selector, and comments, stay visible when you filter for ignored issues, and come back with Un-ignore from the same menu. Ignore is also in the bulk action bar when several issues are selected.
Manage Labels
Open Manage labels… from the label picker to see the whole library; the option only appears for workspace owners and admins. They can Rename label, which updates the name on every issue that carries it, or Delete label and confirm Delete from workspace, which removes the label from every issue while keeping the issues themselves. Shared reports that were already published keep the names they were published with.
Where Labels and Assignees Travel
- Exports: when you export issues to Jira, Linear, Notion, Asana, or Trello, the issue's labels are written into the ticket description as a Labels: line, and the assignee maps through each project's export field picker.
- Shared reports: labels appear as tags on shared issue links, with a label filter (including unlabeled), so a client or stakeholder sees the same categories your team uses.
- MCP: an AI coding agent connected through the OverlayQA MCP server can list, create, and apply labels, assign issues, and filter by label, assignee, creator, or active, finished, and ignored state.
Frequently Asked Questions
Who can create, rename, or delete labels?
Any editor can create a label and apply it to an issue. Renaming a label or deleting it from the workspace requires the workspace owner or an admin, because both actions change every issue that carries the label.
What does the Active issues view include?
Active issues is the default Status filter on the Issues page, the extension, and Team Review. It shows issues that are still open and hides finished ones. Tick a status in the Status filter to see finished work, or use the ignored state to review issues you set aside.
Does ignoring an issue delete it?
No. Ignore hides the issue from the active view and keeps everything attached to it. Choose Un-ignore to bring it back. Use Delete, a separate action with a confirmation step, when you want the issue gone.
Are labels per project or per workspace?
Per workspace. One label library serves every project and every teammate, which is what lets a label filter work across projects and keeps exports and shared reports consistent.