Skip to content

[Due for payment 2025-05-22][Suggested Search v1] [$250] Add grouping to RHP Filters (and other changes to improve UX) #61235

Description

@JmillsExpensify

We're fielding a decent amount of questions across sales/support around how to effectively use Filters, and just as importantly, understand what filter applies to which data type. Accordingly, we're going to apply the following updates to Filters in order to minimize customer confusion and improve overall UX:

  1. Add section headers to the three main types of fitters:
  • General
  • Expenses
  • Reports
  1. Separate each section with a line bar

  2. Rename date filters to make it more clear that they're date filters

  • Submitted to Submitted date
  • Approved to Approved date
  • Paid to Paid date
  • Exported to Exported date
  • Posted to Posted date
  1. Re-arrange the order of filters, anticipating upcoming search functionality
  • The order of the General section is:
    • Type (future consideration; not being changed in this issue)
    • Group by (future consideration; not being changed in this issue)
    • Status (future consideration; not being changed in this issue)
    • From
    • To
    • Has keywords
    • Workspace
  • The order of the Expenses section is:
    • Expense type
    • Merchant
    • Date
    • Total
    • Currency
    • Category
    • Tag
    • Description
    • Card
    • Posted date
    • Tax rate
    • Reimbursable
    • Billable
  • The order of the Reports section is:
    • Report ID
    • Submitted date
    • Approved date
    • Paid date
    • Exported date

All in all, the changes will look like this.

Image

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021917916081372952479
  • Upwork Job ID: 1917916081372952479
  • Last Price Increase: 2025-05-01
  • Automatic offers:
    • nyomanjyotisa | Contributor | 107185962
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions