Skip to content

Report - Currency formatting is not applied to reports after setting in report fields #76767

Closed

Description

@vincdargento

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.2.72-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #71233
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 11/ Chrome
App Component: Workspace Settings

Action Performed:

Pre-conditions:
User has a workspace with USD default currency

  1. Sign in to staging.new.expensify.com
  2. Navigate to Workspace > Workspace settings > Report
  3. In the name field set report title formula to: {report:total} | {report:total:usd} | {report:total:EUR}
  4. Create a new report via FAB
  5. Add transactions totaling $150.50 USD
  6. In the name field set report title formula to: {report:total:jpy} | {report:total:nosymbol} | {report:total:INVALID}
  7. Create a new report via FAB
  8. Add transactions totaling $150.50 USD

Expected Result:

After step 5 report title shows: 150.50 | $150.50 | €150.50
After step 8 report title shows: ¥151 | 150.50 | 0.00

Actual Result:

Currency formatting is not applied in the report title after setting up format in report fields

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

bug.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 4, 2025
  2. melvin-bot commented on Dec 4, 2025

    @melvin-bot

    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.

  3. JmillsExpensify commented on Dec 9, 2025

    @JmillsExpensify
    Contributor

    @neil-marcellini is this a formally supported report title as this point?

  4. JmillsExpensify commented on Dec 9, 2025

    @JmillsExpensify
    Contributor

    We're getting a lot of this report title issues for triaging, though I'm a little unclear if we should be opening all of them up given the recent implementation discussions.

  5. JmillsExpensify commented on Dec 16, 2025

    @JmillsExpensify
    Contributor

    Not sure if this should be prioritize yet

  6. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    @JmillsExpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  7. melvin-bot commented on Dec 20, 2025

    @melvin-bot

    @JmillsExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  8. melvin-bot commented on Dec 23, 2025

    @melvin-bot

    @JmillsExpensify Still overdue 6 days?! Let's take care of this!

  9. melvin-bot commented on Dec 26, 2025

    @melvin-bot

    @JmillsExpensify Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  10. melvin-bot commented on Jan 1, 2026

    @melvin-bot

    This issue has not been updated in over 14 days. @JmillsExpensify eroding to Weekly issue.

  11. JmillsExpensify commented on Jan 13, 2026

    @JmillsExpensify
    Contributor

    Just going to close.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.WeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions