Skip to content

Expense - Incorrect copy for bulk rejecting expenses #84371

Closed

Description

@mitarachim

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: v9.3.32-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #81806
Email or phone of affected tester (no customers): nahemailtest+a462@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11/ Chrome
App Component: Money Requests

Action Performed:

Pre-requisite:
A workspace is set up with approver enabled

Steps:

  1. Sign in to staging.new.expensify.com as a submitter
  2. Submit 2 or more expenses to the workspace
  3. Sign in with the approver account
  4. Navigate to Reports > Expenses
  5. Bulk select expenses from step 2
  6. Click on drop down > Reject

Expected Result:

Copy for reject expense should read as "Explain why you will not approve these expenses."

Actual Result:

Copy for reject expenses reads as "Explain why you will not approve this expense."

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Image

View all open jobs on GitHub

Activity

  1. added 2 commits that reference this issue on Mar 7, 2026
    c7918e9
    bcc16d8
  2. melvin-bot commented on Mar 12, 2026

    @melvin-bot

    Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  3. melvin-bot commented on Mar 16, 2026

    @melvin-bot

    Still overdue 6 days?! Let's take care of this!

  4. melvin-bot commented on Mar 18, 2026

    @melvin-bot

    Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  5. melvin-bot commented on Mar 18, 2026

    @melvin-bot

    Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  6. melvin-bot commented on Mar 19, 2026

    @melvin-bot

    Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  7. melvin-bot commented on Mar 20, 2026

    @melvin-bot

    10 days overdue. I'm getting more depressed than Marvin.

  8. melvin-bot commented on Mar 20, 2026

    @melvin-bot

    10 days overdue. I'm getting more depressed than Marvin.

  9. melvin-bot commented on Mar 25, 2026

    @melvin-bot

    This issue has not been updated in over 14 days. eroding to Weekly issue.

  10. melvin-bot commented on Apr 17, 2026

    @melvin-bot

    This issue has not been updated in over 15 days. eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  11. melvin-bot commented on Jun 29, 2026

    @melvin-bot

    @mitarachim, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions