Skip to content

[Due for payment 2026-08-11] [$250] Add filtering support for Custom Field 1, Custom Field 2, and International Reimbursement IDs on the reports/search page #95389

Closed

Description

@melvin-bot

Summary

PR #90937 added Custom Field 1, Custom Field 2, and International Reimbursement IDs as displayable columns on the reports/expense search page. However, there is currently no way to filter results by these three fields — users can see the values in the table but cannot narrow results by them.

This is a follow-on to the display work and is part of the larger custom columns effort tracked in Expensify/Expensify#622813.

Expected Behavior

Users should be able to filter the reports/expense search results by:

  • Custom Field 1 (report.submitterUserID)
  • Custom Field 2 (report.submitterPayrollID)
  • International Reimbursement IDs (report.orderDealNumbers)

These filters should be accessible from the search/filter UI on the reports page, consistent with how other column-based filters (e.g. submitter, merchant) work today.

Current Behavior

The three fields are displayed as columns (added in PR #90937 / issue #90508) but no corresponding filter options exist in the search filter UI.

References

Issue OwnerCurrent Issue Owner: @mallenexpensify
Upwork Automation - Do Not Edit

Activity

  1. melvin-bot commented on Jul 6, 2026

    @melvin-bot
    Author

    Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)

  2. shubham1206agra commented on Jul 7, 2026

    @shubham1206agra
    Contributor

    @twisterdotcom Can you assign me here? We can use this issue as follow up on #90508?

  3. greg-schroeder commented on Jul 7, 2026

    @greg-schroeder
    Contributor

    Thanks for taking this @shubham1206agra! One of our customers is very keen to know an expected timeline for this adjustment; do you have a general sense of how long it may take to implement? Doesn't have to be perfect, just curious for ballpark.

  4. shubham1206agra commented on Jul 7, 2026

    @shubham1206agra
    Contributor

    @greg-schroeder Do we have an engineer working on BE part of this issue?

  5. greg-schroeder commented on Jul 8, 2026

    @greg-schroeder
    Contributor

    Can you clarify exactly what needs to be done that wasn't done in the initial issue?

  6. dylanexpensify commented on Jul 13, 2026

    @dylanexpensify
    Contributor

    @shubham1206agra can you list out what needs to be done so we can recruit BE engineer?

  7. shubham1206agra commented on Jul 13, 2026

    @shubham1206agra
    Contributor

    @dylanexpensify We need to support submitterUserID, submitterPayrollID, and orderDealNumbers in the query to filter the expenses.

  8. greg-schroeder commented on Jul 16, 2026

    @greg-schroeder
    Contributor

    Posting in the #product thread to get someone involved who can help

  9. 63 remaining items

  10. shubham1206agra commented on Aug 5, 2026

    @shubham1206agra
    Contributor
  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Aug 10, 2026
  12. melvin-bot commented on Aug 10, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  13. melvin-bot commented on Aug 10, 2026

    @melvin-bot
    Author

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
  14. mallenexpensify commented on Aug 13, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @shubham1206agra due $250 via NewDot

    For the deploy blocker > followup. If that should only be due $125 cuz it's a followup, please comment on the issue before payment is due. Thx

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 contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions