search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.46k stars 2.82k forks source link

Dupe detect - Tag name on the confirmation page follows custom tag name from other workspace #50662

Open IuliiaHerets opened 2 hours ago

IuliiaHerets commented 2 hours ago

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: 9.0.48-0 Reproducible in staging?: Y Reproducible in production?: Y Email or phone of affected tester (no customers): applausetester+kh081006@applause.expensifail.com Issue reported by: Applause Internal Team

Action Performed:

Precondition:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat A.
  3. Submit an expense.
  4. Go to workspace chat B.
  5. Submit the same expense as Step 3.
  6. Submit another expense (different amount).
  7. Go back to workspace chat A and open the transaction thread from Step 3 (because Keep this one button won't appear in Step 9 if this is not opened first).
  8. Go to transaction thread of the expense from Step 5.
  9. Click Review duplicates.
  10. Click Keep this one on the second expense in the list (this expense is from Step 3).
  11. Proceed to confirmation page.

Expected Result:

The tag name on the confirmation page will show the custom tag name from workspace A, because the expense from workspace A is selected on review duplicates page (from Step 9).

Actual Result:

The tag name on the confirmation page shows the custom tag name from workspace B, when the expense from workspace A is selected.

Workaround:

Unknown

Platforms:

Screenshots/Videos

https://github.com/user-attachments/assets/ca858588-cf72-414a-8b1b-f3ac4ad63786

View all open jobs on GitHub

melvin-bot[bot] commented 2 hours ago

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

IuliiaHerets commented 2 hours ago

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

IuliiaHerets commented 2 hours ago

@Christinadobrzyn 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