Skip to content

[Due for payment 2026-06-09] [HOLD for #86102] [$250] [CFI] Make the Workspaces list sortable by column headers #89228

Closed

Description

@MelvinBot

Problem

The Workspaces list page in New Expensify does not support sorting by column headers. In Expensify Classic, users could click column headers to sort the workspace list by name or by billing owner.

This is a pain point for customers managing a large number of workspaces — particularly holding companies where a single billing owner oversees workspaces across many independent business units. The billing owner needs to quickly identify workspaces they don't yet own so they can take them over. Without sorting by billing owner, this requires manually scanning through the entire list.

Real-world example: A customer with 174+ workspaces across dozens of business units relied on sorting by billing owner in Classic to find workspaces created by business units (where they were added as admin but not yet the owner). This workflow is now significantly more friction-heavy in New Expensify.

Proposed Solution

Make the Workspaces list sortable by column headers (workspace name, billing owner), similar to how the Spend page tables already support sortable columns. Design has confirmed there are no concerns with this approach — since the workspaces list is displayed as a table, it should be sortable like other tables in the product.

Slack thread: https://expensify.slack.com/archives/C03U7DCU4/p1777580395789969

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022051671377333135794
  • Upwork Job ID: 2051671377333135794
  • Last Price Increase: 2026-05-05
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. johncschuster commented on Apr 30, 2026

    @johncschuster
    Contributor
  2. changed the title [-]Customer Report: Workspace list sorting by column headers not available in New Expensify[/-] [+]Feature Request: Make the Workspaces list sortable by column headers[/+] on May 1, 2026
  3. changed the title [-]Feature Request: Make the Workspaces list sortable by column headers[/-] [+]Make the Workspaces list sortable by column headers[/+] on May 1, 2026
  4. changed the title [-]Make the Workspaces list sortable by column headers[/-] [+][CFI] Make the Workspaces list sortable by column headers[/+] on May 5, 2026
  5. self-assigned this
    on May 5, 2026
  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed on May 5, 2026
  7. 63 remaining items

  8. melvin-bot commented on Jun 3, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  9. added
    ReviewingHas a PR in review
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jun 3, 2026
  10. melvin-bot commented on Jun 8, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  11. melvin-bot commented on Jun 8, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2051671377333135794/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  12. Krishna2323 commented on Jun 8, 2026

    @Krishna2323
    Contributor

    @JS00001 should we add this issue to #86102, or will the payment for this be handled separately?

  13. JS00001 commented on Jun 9, 2026

    @JS00001
    Contributor

    Yeah we can add that as a part of the table cleanup payments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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.ReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions