Skip to content

[$175] Spend - Unable to sort expenses by Vendor #101827

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.91-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #101410
Email or phone of affected tester (no customers): jsdoijnodsdisojo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

Precondition:

  • Connect workspace to Sage Intacct.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create two non-reimbursable expenses.
  4. Add any vendor to the expenses.
  5. Go to Spend > Expenses.
  6. Click Display > Edit columns.
  7. Select Vendor > Save.
  8. Click Vendor title on the table.

Expected Result:

User should be able to sort expenses by Vendor.

Actual Result:

User is not able to sort expenses by Vendor.
Clicking on Vendor does not sort the expenses.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7265803_1790028969925.13.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7265803

Upwork Automation - Do Not Edit

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 22, 2026
  2. applause-bot commented on Sep 22, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/325c02556b1cbf1b05b29019596efe5d727e686f56349d61ebc11ec4e316dd09

  3. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    @Beamanator recently merged #101410, but they are OOO right now, so I'll auto-assign someone else.

  4. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    Triggered auto assignment to @tylerkaraszewski (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. github-actions commented on Sep 22, 2026

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    @Beamanator you have been assigned to this deploy blocker because you reviewed the offending PR: #101410

  7. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    @c3024 you have been assigned to this deploy blocker because you authored the offending PR: #101410

  8. melvin-bot commented on Sep 22, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  9. 34 remaining items

  10. Beamanator commented on Sep 28, 2026

    @Beamanator
    Contributor

    Neither the design doc nor the issue description says anything about sorting the vendor column. This is not a deploy blocker.

    cc: @Beamanator

    I think we should always try to treat the new column like existing expense columns, like tag and category - can you check if those are sortable @c3024 ?

  11. melvin-bot commented on Oct 6, 2026

    @melvin-bot

    @Beamanator @abzokhattab @c3024 this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  12. Beamanator commented on Oct 6, 2026

    @Beamanator
    Contributor

    we reverted the last App PR

  13. c3024 commented on Oct 15, 2026

    @c3024
    Contributor

    NOt overude. Discussion here.

  14. c3024 commented on Oct 25, 2026

    @c3024
    Contributor

    This will be implemented after #104351

  15. c3024 commented on Nov 3, 2026

    @c3024
    Contributor

    I will open the draft Auth PR for review today.

  16. removed their assignment
    on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions