[$1000] [HOLD for payment 2023-06-29] Web - Split Bill - Details page is shown empty for old group chat splits

[kbecciv]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Go to staging dot on web chrome
2. Go to any old group chat where you splitted the bill (Important- split bill report)
3. Click on it and notice that details page is empty
4. But if you split the bill now in the same group and then click on the split bill report, you'll be able to see the details without any problem. Thus the problem occurs for old split bills and not the new ones.

Expected Result:

Details page should be not shown empty for old group chat splits

Actual Result:

Details page is shown empty for old group chat splits

Workaround:

Unknown

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.29.3

Reproducible in staging?: Yes

Reproducible in production?: No

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

Notes/Photos/Videos: Any additional supporting documentation

green-2023-06-19_15.13.45.mp4

Recording.3156.mp4

Expensify/Expensify Issue URL:

Issue reported by: @priya-zha

Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687167180014059

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01034e11a536cbe311
• Upwork Job ID: 1673377762610040832
• Last Price Increase: 2023-06-26

[OSBotify]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @roryabraham (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[roryabraham]

The problem here is that we changed the shape of reportActions data to go from originalMessage.participants -> originalMessage.participantAccountIDs and didn't migrate old reportActions...

[aldo-expensify]

I chatted with Alex. B about this and it seems like we didn't migrate the database data. I'll try to prepare a CQ query to migrate.

[luacmartins]

Removing the blocker label as per this comment