Skip to content

How to Triage Feedback

The Feedback tab is where new bugs, feature requests, change requests, and client-submitted items wait for a first look. Nothing lands on your board or backlog until someone accepts it — or declines it, or merges it into an existing item.

Where Items Come From

Anything can end up needing triage, no matter how it was created — internally, by your team, or from a client. Every item in the queue shows an origin badge so you know where it came from:

  • Client — submitted by a client through their portal.
  • Internal — created by your team.
  • AI — generated by Taskip's AI task generator.
  • Import — added through a CSV import.
  • Workflow — created automatically by a workflow automation.

An item's type (Task, Bug, Feature, Feedback, or Change request) is separate from where it came from — a bug report can come from a client or from your own team, for example. The Feedback tab lists anything still waiting for triage, regardless of its type.

Opening the Feedback Tab

Open a project and select Feedback from the tab bar. The tab shows a count badge whenever items are waiting, and it updates live as new items arrive — you don't need to refresh the page. Clients never see this tab; they see the status of their own submissions elsewhere.

Reading the Queue

Each row shows:

  • A type icon and the item's title (with its task key, if it has one).
  • An origin badge.
  • A similar badge (for example "2 similar") when Taskip's duplicate check finds items that look alike.
  • The priority flag, the requester's avatar, and how long it's been waiting (for example "3d").

Filter the queue by Type, Origin, or Age (1 day, 3 days, 7 days, 30 days, or all), and sort it by Oldest, Newest, or Priority. Select multiple rows with their checkboxes to accept or decline them together.

Accepting an Item

Accepting turns a pending item into planned work in one step. Click the checkmark on a row (or press a with it focused) to open the accept form, where you can set:

  • Type — change it if it was miscategorized.
  • Priority
  • Stage — which board column it lands in (defaults to your first To do stage).
  • Estimate — an optional time estimate.
  • Assignees

Click Confirm to accept it. Nothing here is required — leave a field as-is and Taskip uses the item's current type, its existing priority, and your project's first To do stage.

Declining an Item

Click the X on a row (or press d) to decline it. Choose a reason — Won't do, Duplicate, Cannot reproduce, or Invalid — and optionally add a message the requester will see explaining why. Declined items leave the queue and move into your Done column with a "Declined" chip, so they don't stay in your active columns.

Merging Duplicates

If an item looks like a repeat of existing work, click the merge icon (or press m) to open the merge picker. Taskip suggests likely duplicates first, ranked by match percentage; you can also search by title or task key. Confirm a target and the source item is closed as a duplicate, linked to the item you merged it into. Its comments, files, labels, and watchers move over to the target automatically — nothing is lost, and anyone who was watching the original is added to the item that replaces it.

Keyboard Shortcuts

The Feedback tab is fully usable from the keyboard:

KeyAction
j / kMove focus down / up the list
aAccept the focused item
dDecline the focused item
mMerge the focused item
o or EnterOpen the focused item
EscClose whatever's open

After Triage

Once accepted, declined, reopened, or merged, the same controls follow the item onto its task detail page — a banner above the title shows its triage status (for example "Awaiting triage" with Accept/Decline buttons, or "Declined" with a Reopen button) so you don't need to come back to this tab to act on it later. Anyone who submitted an item can withdraw it themselves while it's still pending.

Who Can Triage

Any staff member can open the Feedback tab and see what's waiting. Accepting, declining, and merging are limited to Admins, Managers, and Project Managers (or a project Lead) — a Member without that access will see a permission error if they try.