Skip to content

[Due for payment 2025-09-02] Export - System message on exported expense, is not fully translated when changing language #68103

Closed

Description

@nlemma

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

  1. Open the staging.new.expensify.com website.
  2. Navigate to "Account" and select "Preferences"
  3. Tap on "Language" and select any language different to english. (For example: Spanish)
  4. Navigate to any workspace chat.
  5. Create a manual expense.
  6. Open the report of the just created expense.
  7. Tap on "More" (Más) and select "Export" (Exportar)
  8. Note that all the exporting options are translated.
  9. Select "All Data - expense level" (Todos los datos - a nivel de gasto) or "All data - report level" (Todos los datos - a nivel de informe).
  10. Dismiss the displayed modal.
  11. 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.

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

Bug6910063_1754548795488.Fully.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 7, 2025
  2. github-actions commented on Aug 7, 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.
  3. melvin-bot commented on Aug 7, 2025

    @melvin-bot

    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.

  4. melvin-bot commented on Aug 7, 2025

    @melvin-bot

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

  5. melvin-bot commented on Aug 7, 2025

    @melvin-bot

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

  6. inimaga commented on Aug 7, 2025

    @inimaga
    Contributor

    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.

  7. 22 remaining items

  8. 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
  9. melvin-bot commented on Aug 26, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  10. melvin-bot commented on Aug 26, 2025

    @melvin-bot

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

  11. melvin-bot commented on Aug 26, 2025

    @melvin-bot

    @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]

  12. NikkiWines commented on Aug 26, 2025

    @NikkiWines
    Contributor

    Fix is on staging, should be deployed to prod soon

  13. melvin-bot commented on Sep 2, 2025

    @melvin-bot

    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.

  14. NikkiWines commented on Sep 4, 2025

    @NikkiWines
    Contributor

    No payment needed here - this was all internal

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions