Set post priority

How to get there: Open any post → side panel → Priority row. Or use the Priority filter in Manage Posts (left sidebar).

Priority is an admin-only label you can attach to any post: Critical, High, Medium, or Low. Customers never see it. Use it to flag the handful of posts your team should not lose track of, sort the backlog, or filter the list down to fires only.

When to use priority

ProductLift already has two ways to rank work:

  • Votes, what customers want most.
  • Prioritization frameworks (RICE, ICE, MoSCoW, etc.), what to build next based on impact/effort math.

Priority is the third lane: a straight admin signal that overrides both. Typical use cases:

  • Tag the 3 bugs that need to ship this sprint as Critical.
  • Mark security or compliance work as High regardless of vote count.
  • Separate "nice to have" tickets from real work without changing their status.

Set the priority

  1. Open the post.
  2. In the right sidebar, find the Priority row.
  3. Click the value. A dropdown appears with None / Critical / High / Medium / Low.
  4. Pick one. It saves immediately.

Pick None to clear it.

You can also set priority on post creation via the API. See ProductLift API, priority body parameter.

Filter and sort by priority

In Manage Posts:

  • The left sidebar has a Priority filter. Pick one value to narrow the list.
  • The Priority column shows the badge inline. It's visible by default, toggle it from the column picker if you don't want it.
  • Click the Priority column header to sort. Sort order is Critical → High → Medium → Low, posts with no priority sort last.

Who can see it

Admins only. Priority is:

  • Never rendered on the public post page, board, or widget.
  • Not exposed in the public API response.
  • Not editable by members or end users.

This matches how Tags work, internal labels for your team that customers never see.

Bulk-setting priority

The Manage Posts page supports bulk actions. Select multiple posts via the checkbox column and pick Set priority from the bulk action menu. See Bulk post operations.

Priority vs MoSCoW

If you're already using the MoSCoW prioritization framework (Must / Should / Could / Won't), you may not need priority too. The difference:

  • MoSCoW is one of several prioritization frameworks, set per portal in Settings → Prioritization framework. It feeds the prioritization score and only shows when MoSCoW is the active framework.
  • Priority is always available regardless of framework, designed for everyday triage rather than formal scoring.

Pick whichever fits your team. Most teams use priority for sprint-level triage and a framework for quarterly planning.