Skip to content

Scan- Wrong IOU details in the notification email #37518

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: 1.4.45-0

Reproducible in staging?: Yes
Reproducible in production?: No
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: Applause internal team
Slack conversation:

Action Performed:

1.Log in in the app
2.Request money to an account that you have access to the email inbox
3.Do not read the message in NewDot to trigger the email notification

Expected Result:

IOU email subject and body display requestee requested amount

Actual Result:

IOU subject : Requestee requested amount
IOU body: Reqestee owes amount

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

Bug6397103_1709216074740!IOUwrong

Add any screenshot/video evidence

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. github-actions commented on Feb 29, 2024

    @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.
  4. melvin-bot commented on Feb 29, 2024

    @melvin-bot

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

  5. m-natarajan commented on Feb 29, 2024

    @m-natarajan
    Author

    @rlinoz 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.

  6. sonialiap commented on Feb 29, 2024

    @sonialiap
    Contributor

    @m-natarajan can you clarify which account's email you're checking? Also what your account relationships are like. The accounts I tested with both own workspaces that the other is a part of. Account A has issued multiple requests (testing), should there be a clean slate - no outstanding expenses?

    I tried

    1. Account A requests from account B
    2. Account B checks email (screenshot below)
    image
  7. puneetlath commented on Feb 29, 2024

    @puneetlath
    Contributor

    This is a back-end issue, so going to remove the DeployBlockerCash label.

  8. rlinoz commented on Mar 4, 2024

    @rlinoz
    Contributor

    Related to #35353, will take a look later.

  9. rlinoz commented on Mar 6, 2024

    @rlinoz
    Contributor

    Done with the other issue, going to take a look at this tomorrow.

  10. rlinoz commented on Mar 14, 2024

    @rlinoz
    Contributor
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.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions