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
Per diem - The string "Qty" in the Confirm details page is not translated into Spanish #54902
Version Number: 9.0.81-3 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail:#54252 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Windows 10/ Chrome, Samsung S23FE/ Android 14 App Component: Money Requests
Action Performed:
Precondition
Workspace has Per diem enabled and Per diem rates loaded.
The selected language in Preferences is Spanish.
Steps:
Go to staging.new.expensify.com
Go to FAB > Create expense > Per diem tab
Select any country
Select start and end dates
Select any Subrate
Enter any Quantity
Click on Save
Expected Result:
The string "Qty" in the Confirm details page is translated into Spanish.
Target string: Qty
Suggested string: Cant
Actual Result:
The string "Qty" in the Confirm details page is not translated into Spanish.
👋 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.
@VictoriaExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
Activity
melvin-bot commentedon Jan 7, 2025
Triggered auto assignment to @thienlnam (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jan 7, 2025
Triggered auto assignment to @VictoriaExpensify (
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 Jan 7, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jan 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:
vincdargento commentedon Jan 7, 2025
@VictoriaExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
thienlnam commentedon Jan 7, 2025
Behind beta so not a blocker - cc @shubham1206agra looks like an easy one to add into your PR
shubham1206agra commentedon Jan 8, 2025
Will be fixed in
https://github.com/Expensify/App/pull/54760/commits/6aa760e40347c306df3b1da99e9bb5abf1537132VictoriaExpensify commentedon Jan 9, 2025
Closing this out since it will be fixed in the above mentioned GH