Skip to content

Copy of the paying automatically report is wrong #62635

Closed

Description

@jponikarchuk

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.1.49-9
Reproducible in staging?: Yes
Reproducible in production?: Unable to check, new feature
If this was caught during regression testing, add the test name, ID and link from TestRail: #60171
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Android 13 / Xiaomi Poco F5, Windows 11 / Chrome. iOS 15.8.3 / iOS 15.8.3
App Component: Other

Action Performed:

Precondition:

  • Already setup the BA account and Wallet bank account for the Payer
  1. Go to Settings > Workspaces > Rules
  2. Turn on the "Auto-pay approved reports" option
  3. Create an expense on the workspace
  4. Submit and approve
  5. Wait for it to be paid automatically
  6. Verify that the copy should read "paid with Expensify via workspace rules"

Expected Result:

Verify that the copy should read "paid $XX.XX with Expensify via workspace rules"
Please check this GH for more details of copy report action message #60035

Actual Result:

The copy of the paying automatically report is still using old text, the report action that appear is "automatically paid $XX.XX with Expensify via workspace rules"

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

Image

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 23, 2025
  2. melvin-bot commented on May 23, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. melvin-bot commented on May 23, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 23, 2025

    @melvin-bot

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

  5. github-actions commented on May 23, 2025

    @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. nyomanjyotisa commented on May 23, 2025

    @nyomanjyotisa
    Member

    The orignal PR was reverted here

  7. techievivek commented on May 23, 2025

    @techievivek
    Contributor

    🚀 Cherry-picked to staging by https://github.com/JS00001 in version: 9.1.49-9 🚀

    From the OP, the QA was done on v9.1.49-9, which already includes the revert you mentioned. So it's unclear how the issue is still reproducible on that same version. I'll check in with the QA team to confirm.

  8. IuliiaHerets commented on May 23, 2025

    @IuliiaHerets

    @techievivek Issue is still reproducible on the latest build (9.1.49-9), system message changes from Automatically paid.. to Paid... after refreshing/reopening the report

    bandicam.2025-05-23.11-28-30-066.mp4
  9. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on May 23, 2025
  10. mountiny commented on May 23, 2025

    @mountiny
    Contributor

    Since this is just reverting to the previous copy, no need to block

  11. techievivek commented on May 23, 2025

    @techievivek
    Contributor

    Since this is just reverting to the previous copy, no need to block

    Aaah ok, that makes sense, not sure why QA didn't realize that and reported as a bug. I think we can just close this since the original issue needs to be worked again.

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.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions