-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[$250] [Dupe detection] Use new ResolveDuplicates when approver is resolving duplicates #48416
Comments
@parasharrajat I am assigning you as the C+ in this issue since you reviewed the main ones. |
Sure |
Triggered auto assignment to @sonialiap ( |
Job added to Upwork: https://www.upwork.com/jobs/~011781060ec2a6c428 |
Current assignee @parasharrajat is eligible for the External assigner, not assigning anyone new. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Add a new command for admin/approver when resolving the duplicate transaction from submitter What is the root cause of that problem?We're always calling App/src/pages/TransactionDuplicate/Confirmation.tsx Lines 45 to 48 in e60b821
What changes do you think we should make in order to solve the problem?
Lines 3074 to 3079 in e60b821
What alternative solutions did you explore? (Optional) |
The proposal sounds good @nkdengineer sounds good to me. 🎀 👀 🎀 C+ reviewed |
Current assignee @pecanoro is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
Assigning @nkdengineer! |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Will raise the PR tomorrow. |
@pecanoro In the |
A comma-separated list of report actions |
@pecanoro Can you give an example? Do we need to add |
Imagine we have 3 duplicates with transactionIDs 111, 222 and 333. We want to keep 111 and hold the other two. Then:
Nope, no reportID since they are not changing reports |
@pecanoro I mean I need an example for |
@pecanoro When I call
Screen.Recording.2024-09-09.at.11.35.19.mov |
Oh, it's a BE problem, I j just checked the logs. Let me create a PR to fix it |
The PR is merged, we are waiting for a deploy and then you will be able to use the endpoint in staging again. I renamed transactionIDToKeep for just transactionID |
@nkdengineer PR is deployed to prod now! |
@parasharrajat The PR is here. |
What do you mean by NVP @pecanoro? |
@pecanoro While testing I found another BE bug, the dismiss violation action isn't stored from BE side. |
Ah sorry, when the transaction is put on HOLD, we add a value to the transaction namevaluepairs in the comment. |
Are you sure? It is added for the transaction we want to keep, not for the others. |
Yes, I tested and after reset cache this action is removed since BE doesn't return this action. Also the resolve duplicate API doesn't return dismiss violation action data. |
Let me double-check manually, but it's pretty odd since I even wrote automated tests for this and they are passing |
@nkdengineer Can you paste here what the BE is returning for you? |
|
@pecanoro The response here. |
There is something off, also because both hold actions are returned for the same report |
Ah nvm, forget my previous comment, you were resolving duplicates with only two transactions. I am going to check the database |
Ah I found the problem, another parameter name that got cleared because of sanitization. I am going to rename it to something better either way. I will create a PR in the back-end |
@nkdengineer BE fix is on staging, you can test it in the PR now! New parameter is called |
@pecanoro Does this change affect |
@parasharrajat No, it should not change it |
Got it. Thanks. |
Note for future: I noticed that when admin resolves a duplicate, the transaction is no more duplicate for admin but same transaction still shown duplicate for the original user who requested. I confirmed that this is expected #48522 (comment) |
@parasharrajat The original PR was reverted so I created a new one here to fix another bug #49900 |
Part of the Duplicate Detection project
Main issue: https://github.com/Expensify/Expensify/issues/411008
Project: Dupe detection
Feature Description
Right now, we always call MergeTransactions when resolving duplicates and click
Confirm
at the last page of resolving duplicates. However, we need to call a new command calledResolveDuplicates
when an approver or admin (basically anyone but the submitter) is the person resolving the duplicates. The behaviour (so we can create the proper optimistic actions) should be as follows:This command will update the transaction to match the fields we chose during the flow. It should already be doing this.
Main issue: https://github.com/Expensify/Expensify/issues/411008
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @The text was updated successfully, but these errors were encountered: