Skip to content

[Pending / Scanning] Message containing a report says it is from the workspace name instead of the cardholder's name #49036

Closed

Description

@m-natarajan

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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @kevinksullivan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1726081403491199

Action Performed:

  1. Get assigned a >$0 limit on cardtest.expensify.com domain
  2. Navigate to NewDot in your test account, and go to Settings > Wallet > Expensify Card > Reveal details (on virtual card)
  3. Navigate to this paypal link and select “buy” on the first button on that screen, and use your virtual card details to make the purchase.
  4. Check workspace chat

Expected Result:

Cardholder's name displayed in report

Actual Result:

Message containing a report says it is from the workspace name. Same issue observed for IOUs as well

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

image (7)

image (8)

Add any screenshot/video evidence

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 12, 2024
  2. melvin-bot commented on Sep 12, 2024

    @melvin-bot

    Triggered auto assignment to @miljakljajic (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. MelvinBot commented on Sep 12, 2024

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  4. moved this to Release 2: Summer 2024 (Aug) in [#whatsnext] #wave-collecton Sep 12, 2024
  5. changed the title [-]Message containing a report says it is from the workspace name instead of the cardholder's name[/-] [+][Pending / Scanning] Message containing a report says it is from the workspace name instead of the cardholder's name[/+] on Sep 12, 2024
  6. moved this from Release 2: Summer 2024 (Aug) to Release 2.5: SuiteWorld (Sept 9th) in [#whatsnext] #wave-collecton Sep 12, 2024
  7. kevinksullivan commented on Sep 12, 2024

    @kevinksullivan
    Contributor
  8. self-assigned this
    on Sep 12, 2024
  9. grgia commented on Sep 13, 2024

    @grgia
    Contributor
  10. grgia commented on Sep 13, 2024

    @grgia
    Contributor

    Pasting from slack:

    Seems the issue might is from this line here, which is causing the second part of this line to always be true

     const isWorkspaceActor = isInvoiceReport || (ReportUtils.isPolicyExpenseChat(report) && (!actorAccountID || displayAllActors));
    
  11. 12 remaining items

  12. melvin-bot commented on Sep 30, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  13. melvin-bot commented on Sep 30, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  14. melvin-bot commented on Sep 30, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  15. melvin-bot commented on Oct 31, 2024

    @melvin-bot

    This issue has not been updated in over 15 days. @grgia eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  16. grgia commented on Nov 1, 2024

    @grgia
    Contributor

    Closing as complete

  17. moved this from Release 2.5: SuiteWorld (Sept 9th) to Done in [#whatsnext] #wave-collecton Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.InternalRequires API changes or must be handled by Expensify staffMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions