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
[Due for payment 2025-09-02] Export - System message on exported expense, is not fully translated when changing language #68103
Version Number: 9.1.90-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from TestRail:#64616 Email or phone of affected tester (no customers):ibellicotest+1540@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 10 / Chrome App Component: Other
Action Performed:
Prerequisite: Account has at least one workspace.
Open the staging.new.expensify.com website.
Navigate to "Account" and select "Preferences"
Tap on "Language" and select any language different to english. (For example: Spanish)
Navigate to any workspace chat.
Create a manual expense.
Open the report of the just created expense.
Tap on "More" (Más) and select "Export" (Exportar)
Note that all the exporting options are translated.
Select "All Data - expense level" (Todos los datos - a nivel de gasto) or "All data - report level" (Todos los datos - a nivel de informe).
Dismiss the displayed modal.
Note that the system message generated with the export, is not fully translated.
Expected Result:
When changing the language on the app, the system message generated after exporting to "All Data" should be fully translated.
Actual Result:
When changing the language of the app to Spanish, the system message generated after exporting to "All Data" is not fully translated. The system message is displayed as "Exportado a All Data - Expense level Export".
This issue is reproducible in every language.
👋 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.
This is a bug with mistranslation of the new enhanced export features implemented in #64616. cc: @NikkiWines
Don't think it warrants being a deploy-blocker on its own though.
changed the title [-]Export - System message on exported expense, is not fully translated when changing language[/-][+][Due for payment 2025-09-02] Export - System message on exported expense, is not fully translated when changing language[/+]on Aug 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.98-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@NikkiWines@NicMendonca The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Activity
github-actions commentedon Aug 7, 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:
melvin-bot commentedon Aug 7, 2025
Triggered auto assignment to @NicMendonca (
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 Aug 7, 2025
Triggered auto assignment to @inimaga (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 7, 2025
💬 A slack conversation has been started in #expensify-open-source
inimaga commentedon Aug 7, 2025
This is a bug with mistranslation of the new enhanced export features implemented in #64616. cc: @NikkiWines
Don't think it warrants being a deploy-blocker on its own though.
22 remaining items
[-]Export - System message on exported expense, is not fully translated when changing language[/-][+][Due for payment 2025-09-02] Export - System message on exported expense, is not fully translated when changing language[/+]melvin-bot commentedon Aug 26, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.98-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-09-02. 🎊
melvin-bot commentedon Aug 26, 2025
@NikkiWines @NicMendonca The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
NikkiWines commentedon Aug 26, 2025
Fix is on staging, should be deployed to prod soon
melvin-bot commentedon Sep 2, 2025
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
NikkiWines commentedon Sep 4, 2025
No payment needed here - this was all internal