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

Duplicate Policy Expense Chats on a Migrated Policy #54333

Closed
1 of 8 tasks
m-natarajan opened this issue Dec 18, 2024 · 12 comments
Closed
1 of 8 tasks

Duplicate Policy Expense Chats on a Migrated Policy #54333

m-natarajan opened this issue Dec 18, 2024 · 12 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Needs Reproduction Reproducible steps needed

Comments

@m-natarajan
Copy link

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:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @mountiny
Slack conversation (hyperlinked to channel name): migrate

Action Performed:

  1. Log into the newdot
  2. Navigate to the migrated policy
  3. Observe multiple expense chats listed under this policy

Expected Result:

Users should see only one policy expense chat for the migrated policy

Actual Result:

Multiple policy expense chats appear for the same

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

image (19)

image (20)

View all open jobs on GitHub

@m-natarajan m-natarajan added Daily KSv2 Needs Reproduction Reproducible steps needed Bug Something is broken. Auto assigns a BugZero manager. labels Dec 18, 2024
Copy link

melvin-bot bot commented Dec 18, 2024

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

@MelvinBot
Copy link

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

@mountiny
Copy link
Contributor

This might not be necesarilly related to migration but might be related to some bugs in the change policy command back then. Lets see if I will run into a fresh case

@flaviadefaria
Copy link
Contributor

I'll put this as high for now until we confirm if this was more of an edge case or not.

@flaviadefaria flaviadefaria moved this to First Cohort - HIGH in [#whatsnext] #migrate Dec 19, 2024
@mountiny
Copy link
Contributor

Oh I think that I see the pattern, they all have this change policy from EXFY Finance on April 17th 2024

image

This is when I was moving from a UK entity to contracting, and Jenna had to move me across the policies in the domain. So I guess it somehow took expenses from the other testing workspaces and put it onto the main one Jenna added me on but somehow created multiple workspace chats 😢

@michaelkwardrop
Copy link
Contributor

@mountiny should I try reproducing? What steps do I need to take to create a migrated policy/ workspace?

@mountiny
Copy link
Contributor

I dont think this will be easy to reproduce, the migrated policies are quite unique now and i feel like this is all combination of our accounts being on domain control which probably brings in more edge cases.

@NikkiWines @greg-schroeder you have recently been moved between the policies i assume. Can you find multiple workspace chats in your account for the new UK or previous US policy maybe?

@NikkiWines
Copy link
Contributor

I can't reproduce that bug, sorry :(

@mountiny
Copy link
Contributor

No problem. This was a long time ago so if you have been moved across the policies without issues i would consider it as good to close personally.

@greg-schroeder
Copy link
Contributor

I also tried and couldn't repro as outlined here, sorry @mountiny :/

@michaelkwardrop
Copy link
Contributor

@mountiny should we close out or add the retest weekly label?

@mountiny
Copy link
Contributor

I think we can close this and see if anyone can run into this again.

I am quite confident this was caused by the change of entities as it aligns too well not to be true. Since Nikki and Greg just went through the same changes and they do not see multiple workspaces, i think we can close and assume this was fixed in this flow

@melvin-bot melvin-bot bot added the Overdue label Dec 22, 2024
@mountiny mountiny closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2024
@melvin-bot melvin-bot bot removed the Overdue label Dec 22, 2024
@github-project-automation github-project-automation bot moved this from First Cohort - HIGH to Done in [#whatsnext] #migrate Dec 22, 2024
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. Daily KSv2 Needs Reproduction Reproducible steps needed
Projects
Development

No branches or pull requests

7 participants