You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Copy of the paying automatically report is wrong #62635
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
Go to Settings > Workspaces > Rules
Turn on the "Auto-pay approved reports" option
Create an expense on the workspace
Submit and approve
Wait for it to be paid automatically
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"
👋 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:
Identify the pull request that introduced this issue and revert it.
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.
@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
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.
Activity
melvin-bot commentedon May 23, 2025
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.melvin-bot commentedon May 23, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 23, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 23, 2025
👋 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:
nyomanjyotisa commentedon May 23, 2025
The orignal PR was reverted here
techievivek commentedon May 23, 2025
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.
IuliiaHerets commentedon May 23, 2025
@techievivek Issue is still reproducible on the latest build (9.1.49-9), system message changes from
Automatically paid..toPaid...after refreshing/reopening the reportbandicam.2025-05-23.11-28-30-066.mp4
mountiny commentedon May 23, 2025
Since this is just reverting to the previous copy, no need to block
techievivek commentedon May 23, 2025
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.