-
Notifications
You must be signed in to change notification settings - Fork 3k
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] Old Expense Threads displaying in the LHN for Migrated User #55410
Comments
Triggered auto assignment to @JmillsExpensify ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
@JmillsExpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Let's make this issue only about old expense threads in the LHN, supportal access should be handled in #retain and I haven't seen this come up again. |
Job added to Upwork: https://www.upwork.com/jobs/~021881829546506566300 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Sounds good. I'll open it up to the community. |
Do we have better reproduction steps here? I am not sure what we mean by have a user migrated with old expense threads. |
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: @quinthar
Slack conversation (hyperlinked to channel name): migrate
Action Performed:
Expected Result:
Old expense threads should be properly excluded during migration and not appear in the LHN.
Actual Result:
Old expense threads are visible in the LHN.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Screenshots and video can be viewed in OP
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mananjadhavThe text was updated successfully, but these errors were encountered: