Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review duplicates - Review duplicates button does not disappear after the expense is paid #51141

Open
8 tasks done
IuliiaHerets opened this issue Oct 20, 2024 · 17 comments
Open
8 tasks done
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering Internal Requires API changes or must be handled by Expensify staff Reviewing Has a PR in review Weekly KSv2

Comments

@IuliiaHerets
Copy link

IuliiaHerets commented Oct 20, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Version Number: 9.0.51-1
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create a new workspace.
  3. Submit an expense to the workspace chat.
  4. Pay the expense.
  5. Submit the same expense in Step 3 to the workspace chat.
  6. Click on the expense preview.
  7. Click Pay elsewhere and pay it.

Expected Result:

Review duplicates button will disappear after the expense is paid.

Actual Result:

Review duplicates button does not disappear after the expense is paid. It only disappears after the page is refreshed.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6640180_1729422842946.20241020_184629.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @marcochavezf
@IuliiaHerets IuliiaHerets added DeployBlockerCash This issue or pull request should block deployment Bug Something is broken. Auto assigns a BugZero manager. labels Oct 20, 2024
Copy link

melvin-bot bot commented Oct 20, 2024

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

@melvin-bot melvin-bot bot added the Daily KSv2 label Oct 20, 2024
Copy link

melvin-bot bot commented Oct 20, 2024

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

Copy link

melvin-bot bot commented Oct 20, 2024

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

@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Oct 20, 2024
Copy link
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.

@IuliiaHerets
Copy link
Author

We think that this bug might be related to #wave-control

@Shahidullah-Muffakir
Copy link
Contributor

Related PR #50133

@daledah
Copy link
Contributor

daledah commented Oct 21, 2024

This is likely a BE Bug, as PayMoneyRequest doesn't remove transactionViolations in Onyx:

Screenshot 2024-10-21 at 12 07 40 Screenshot 2024-10-21 at 12 08 19

We can add optimistic data to remove transactionViolations from the FE side, but I think we should apply the same change to BE as well.

@adelekennedy
Copy link

adelekennedy commented Oct 21, 2024

this is high priority but imo shouldn't delay deploys etc - @marcochavezf if you disagree!

@adelekennedy adelekennedy removed the DeployBlockerCash This issue or pull request should block deployment label Oct 21, 2024
@marcochavezf
Copy link
Contributor

marcochavezf commented Oct 21, 2024

Yup, sounds good, it shouldn't be a deploy blocker and I agree this should be fixed in the BE

@marcochavezf marcochavezf added Daily KSv2 Internal Requires API changes or must be handled by Expensify staff and removed Hourly KSv2 labels Oct 21, 2024
@melvin-bot melvin-bot bot added the Overdue label Oct 23, 2024
@adelekennedy
Copy link

@marcochavezf con contributors help here at all or is this an entirely BE issue you're working on?

@melvin-bot melvin-bot bot removed the Overdue label Oct 23, 2024
@marcochavezf
Copy link
Contributor

I think this is entirely BE, I'm fixing another priority bug, I will come back to this one tomorrow

Copy link

melvin-bot bot commented Oct 28, 2024

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

@melvin-bot melvin-bot bot added the Overdue label Oct 28, 2024
@marcochavezf
Copy link
Contributor

Continuing with investigation today

@melvin-bot melvin-bot bot removed the Overdue label Oct 28, 2024
@marcochavezf
Copy link
Contributor

I asked internally what would be the better solution in the BE

@marcochavezf
Copy link
Contributor

PR in review for BE fix

@marcochavezf
Copy link
Contributor

marcochavezf commented Oct 30, 2024

I quickly created a PR for the optimistic values. It's on hold for the BE fix.

@allgandalf
Copy link
Contributor

Please assign me here for payment, I will be reviewing the attached PR #51770

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Engineering Internal Requires API changes or must be handled by Expensify staff Reviewing Has a PR in review Weekly KSv2
Projects
None yet
Development

No branches or pull requests

6 participants