Skip to content

Attendees - Attendees field shows "Attendees per person" while receipt is scanning #59597

Closed

Description

@IuliiaHerets

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.23-1
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: #58120
Email or phone of affected tester (no customers): sdjmosdjojsoid@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Click + > Create expense > Scan.
  4. Upload a receipt.
  5. On confirmation page, click Attendees.
  6. Select another user and click Save.
  7. Note that Attendees field shows "Attendees • MYR 0.00 per person".
  8. Create the expense.
  9. Go to transaction thread.

Expected Result:

Attendees field will show "Attendees • MYR 0.00 per person" in the transaction thread while the receipt is scanning.

Actual Result:

Attendees field shows "Attendees per person" in the transaction thread while the receipt is scanning.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6791350_1743697660302.20250404_002441.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @VictoriaExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 3, 2025
  2. melvin-bot commented on Apr 3, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Apr 3, 2025

    @melvin-bot

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

  4. melvin-bot commented on Apr 3, 2025

    @melvin-bot

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

  5. github-actions commented on Apr 3, 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.
  6. IuliiaHerets commented on Apr 3, 2025

    @IuliiaHerets
    Author

    I added a blocker label, as it is not repro on prod, it is a new feature.
    If there is no need to add this label, please let me know, and I will delete it. If not, you can also do it yourself.

  7. samranahm commented on Apr 3, 2025

    @samranahm
    Contributor

    🚨 Edited by proposal-police: This proposal was edited at 2025-04-03 16:58:27 UTC.

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Attendees - Attendees field shows "Attendees per person" while receipt is scanning

    What is the root cause of that problem?

    Here

    iouAttendees?.length && iouAttendees.length > 1 ? `\u00B7 ${formattedAmountPerAttendee} ${translate('common.perPerson')}` : ''

    we have another format as compared to

    Array.isArray(transactionAttendees) && transactionAttendees.length > 1 ? `${formattedPerAttendeeAmount} ${translate('common.perPerson')}` : ''

    What changes do you think we should make in order to solve the problem?

    We need to change this translation to

    Array.isArray(transactionAttendees) && transactionAttendees.length > 1 ? `${formattedPerAttendeeAmount} ${translate('common.perPerson')}` : ''

    transactionAttendees?.length && transactionAttendees.length > 1 ? `\u00B7 ${formattedPerAttendeeAmount} ${translate('common.perPerson')}` : ''

    What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

    Use the same format

    What alternative solutions did you explore? (Optional)

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  8. jasperhuangg commented on Apr 3, 2025

    @jasperhuangg
    Contributor

    Reached out here to @allroundexperts to see if they can fix this, coming from #58120

  9. 29 remaining items

  10. melvin-bot commented on Apr 16, 2025

    @melvin-bot

    Triggered auto assignment to @alexpensify (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.

  11. mallenexpensify commented on Apr 16, 2025

    @mallenexpensify
    Contributor

    @alexpensify Vic is out, can you please wrap this issue up? Thx

  12. allroundexperts commented on Apr 16, 2025

    @allroundexperts
    Contributor

    @mallenexpensify This is still being worked on here. Let's keep this open.

  13. changed the title [-][Due for payment 2025-04-16] [Due for payment 2025-04-14] Attendees - Attendees field shows "Attendees per person" while receipt is scanning[/-] [+]Attendees - Attendees field shows "Attendees per person" while receipt is scanning[/+] on Apr 16, 2025
  14. added and removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Apr 16, 2025
  15. removed their assignment
    on Apr 16, 2025
  16. alexpensify commented on Apr 16, 2025

    @alexpensify
    Contributor

    Since this last PR is still being worked on, I've updated the GH to remove the payment notices. @allroundexperts, please leave a comment when you are ready, and we can update the GH again. For now, I'll remove myself here, and Vic should be back for the payment date when the next PR is live. If anything changes this week, @ me and I'll hop back in to help.

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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions