The backlog is where Pilea’s analysis becomes your team’s work queue. Every item carries its evidence with it - mention count, customer count, deal size (revenue), themes, tags, assignee, commenters, and the date it was last mentioned - so you never have to ask “why is this here?”

Three views, one backlog

Switch between Table, List, and Kanban views. They show the same items, just organized differently. On the kanban board, the columns are the triage statuses - so moving a card is triaging it.

Triage statuses

Every backlog item has one status:

Status	What it means
📬 New	Just arrived - not yet triaged
💾 Saved	Reviewed and kept for later
🧑‍💻 Ready for Dev	Specced and ready to pick up
🚶 In Progress	Someone’s working on it
🧪 Ready for Test	Built, awaiting verification
✅ Completed	Shipped and done
🚫 Won’t Do	Deliberately declined
📦 Archived	Out of the active backlog
💤 Snoozed	Parked - revisit later

Item types and sizes

Item types come from your workspace’s analysis framework. With the Backlog Management framework, for example, items are classified as 🚀 Feature, ✨ Improvement, 🐛 Bug, or 🔧 Technical Debt.

Each item also gets a size from XS to XL. Sizes aren’t just labels - they feed the effort divisor in priority scoring, so small high-signal items float above large ones.

Finding what you need

Use search plus filters for Type, Status, Assignee, Customer, Tag, Theme, and Date. Completed and archived items are tucked away by default - flip the Show completed/archived switch to bring them back.

Sort options include Priority Score; the default sort is Last Mentioned, so fresh customer signal surfaces first.

At the top of the page, collapsible stats cards show Items Crunched, Time to Triage, Time to Complete, and Customer Sentiment. And if you want fresh scores right now instead of waiting for the next automatic run, click Recalculate scores.

Working in bulk

Multi-select items to act on many at once. Spotted duplicates? Select them and use Merge to combine them into a single item - their evidence comes along for the ride.

💡 Tip: Merging duplicates isn’t just tidying. Consolidated items concentrate their mentions and customers in one place, which gives you a truer picture of demand.

Exporting to your issue tracker

When an item is ready to build, send it where your engineers live:

Open the item and go to its Details tab.
Under the Export to Issue Tracker section, you’ll see a button for each tracker you’ve connected.
Click it (for example Export to Linear), then pick the project or repo.

Already-exported items show a link, so you can jump straight to the issue - and you won’t accidentally export the same item twice.

ℹ️ Note: Exporting doesn’t remove the item from Pilea. It stays in your backlog with all its customer evidence intact.

Next: How the Pilea priority score works

Managing your backlog