[BE - Requires Internal Engineer] Expense - Expense details disappear when opening expense after workspace is deleted

[lanitochka17]

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.56-2 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: N/A 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. Go to workspace chat
4. Submit an expense
5. Go to Account settings > Workspaces
6. Delete the workspace
7. Go back to Inbox (on web, it will auto open the expense details)
8. (mobile only) open the workspace chat and then open the expense

Expected Result:

Expense details will not disappear when opening expense after the workspace is deleted

Actual Result:

Expense details disappear when opening expense after the workspace is deleted

Workaround:

Unknown

Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/387fb4cc-1885-463d-b0fe-139b4f6c68e8

View all open jobs on GitHub

[melvin-bot[bot]]

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

[FitseTLT]

This is a BE bug. On Open Report it is resetting the parent report id of the expense report.

[zanyrenney]

Thanks for figuring that out for us @FitseTLT

[melvin-bot[bot]]

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

[zanyrenney]

waiting on internal engineers in quality for this

[zanyrenney]

Hmmm, maybe actually this is more fitting for expense!

[melvin-bot[bot]]

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

[zanyrenney]

This is waiting on an engineer to pick up. It has been triaged but expense is not as high priority as our other waves. Changing to weekly for now.

[melvin-bot[bot]]

@zanyrenney this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[zanyrenney]

This is considered a bug/follow up. Seeing as expense is lower priority and there are a shortage of engineers to pick this up, this is still the appropriate label and prioritisation.

[zanyrenney]

Same as above, I think we can hold on this for now, keep it as weekly.

[melvin-bot[bot]]

This issue has not been updated in over 15 days. @zanyrenney eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[zanyrenney]

I think Monthly is the right prioritisation.

[zanyrenney]

Waiting on internal capacity for this one.

[zanyrenney]

downgraded.

[zanyrenney]

I actually will retest again as this has been open a while.

[zanyrenney]

I can no longer reproduce this so I think it's fine to close this out!