Requests filter rework

Rework Filtering in Requests and Roadmaps so teams can find and combine the information they need through one consistent filter menu:

Filter options

• Status - select individual workflow statuses.

• Status type - select broad workflow types, covering all statuses within each type.

• Category - select one or more categories.

• Labels - select individual labels or a whole label group. Selecting a group matches any label within it. Support “No label,” including no label within a specific group.

• Form fields - filter by the request’s custom field values, with operators appropriate to each field type.

• Insights - filter by the number of linked insights, including zero, minimum, maximum, and ranges.

• Impact - Filter by the individual follow-up answers, including unanswered. Keep these separate from the combined Importance score used for ordering.

  • Importance

  • Urgency

  • Usage frequency

• Requesters - match customers who requested the feature.

  • Count - minimum, maximum, exact count, or range.

  • MRR - the MRR of requesters

  • Customer - select specific requesters.

  • Company - select companies represented by requesters.

  • Segment - requesters belonging to selected segments.

  • Customer attributes - attributes of the requesters.

  • Company attributes - attributes of the requesters’ companies.

• Author - match the request’s author.

  • Customer - select the author.

  • Company - the author’s company.

  • Segment - segments the author belongs to.

  • Customer attributes - the author’s attributes.

  • Company attributes - attributes of the author’s company.

• Assignee - select teammates, including “Me” and “No assignee.”

• Dates - Provide relative presets and “Custom date or timeframe.” Support before, after, and between, plus “Not set” where relevant. Due dates also need future presets and “Overdue.” Treat time in status as a duration, with minimum, maximum, and range options.

  • Due date

  • Created date

  • Updated date - latest change to the request’s content or properties.

  • Status updated date - latest workflow status change.

  • Completed date - latest transition into a completed status.

  • Triaged date - when the latest required triage review was completed.

  • Time in current status - elapsed time since entering the current status. Comments and other edits must not reset it.

• Visibility

  • Visible on portal

  • Author only

  • Internal

• Source - multi-select the channels where feedback originated (e.g. Slack, Public portal, Support, and Feedback widget). A request can match multiple sources through its linked feedback. Include “No source” for missing origin data.

• Integrations - select an integration, such as Jira or Linear, then filter for linked or unlinked requests.

Filter behavior

• Support AND / OR groups, including nested groups.

• Support inclusion and exclusion. Labels should support matching any, all, or none of the selected labels.

• Requester filters match at least one requester. Combined conditions within one requester group must match the same customer and their company.

• Show a short initial list in customer and company selectors before typing, then allow search.

• Make the whole filter menu searchable, including nested options.

• Save filters with saved views. Relative date filters should update automatically over time.

• Use consistent filtering in Requests and Roadmaps. Additional roadmap filters should narrow the roadmap’s configured scope.