-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search - No "exported to CSV" system message and invalid data in downloaded CSV file #47741
Comments
Triggered auto assignment to @CortneyOfstad ( |
Triggered auto assignment to @tgolen ( |
👋 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:
|
We think that this bug might be related to #wave-collect - Release 1 |
We reverted the offending PR. Closing. |
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.0.22-7
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://expensify.testrail.io/index.php?/tests/view/4874296
Email or phone of affected tester (no customers): applausetester+kh050806@applause.expensifail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
In Step 11, there will be "exported to CSV" system message in the expense report.
In Step 12, the CSV file will show the correct expense details.
Actual Result:
In Step 11, there is not "exported to CSV" system message in the expense report.
In Step 12, the CSV file shows invalid data.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6577258_1724173096081.20240821_005406.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: