Skip to content

IOU - Amount is not updated and requester name and avatar are duplicated after changing IOU amount #24585

Closed

Description

@lanitochka17

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to + > Request money
  3. Complete the request money flow
  4. Click on IOU report preview
  5. Click on the IOU preview in IOU thread
  6. Click on the IOU amount
  7. Change the IOU amount
  8. Navigate to IOU thread
  9. Navigate to the conversation with the owed user

Expected Result:

In Step 7 and 8. the IOU shows the updated amount
In Step 9, the IOU user names and avatars should remain as those of User A and User B

Actual Result:

In Step 7 and 8. the IOU does not show the updated amount
In Step 9, the IOU user names and avatars change from User A & User B to User A & User A

Workaround:

Unknown

Platforms:

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

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.54.7

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6165743_20230815_200843.1.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. OSBotify commented on Aug 15, 2023

    @OSBotify
    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.
  2. melvin-bot commented on Aug 15, 2023

    @melvin-bot

    Triggered auto assignment to @aldo-expensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  3. mountiny commented on Aug 15, 2023

    @mountiny
    Contributor

    This is not a deploy blocker, this is expected for this new feature and will be fixed as a follow up #23961

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions