mWeb - Chat -Drafted message is not moving to the top after made drafted message, only after refresh the page

[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!

---

Issue found when executing PR #11211

Action Performed:

1. Go to staging.new.expensify.com
2. Log in with the expensifail account
3. Make sure you are in default view mode
4. Make sure you have several pinned chats
5. Verify the group of pinned chats are sorted alphabetically in the LHN
6. Pin a new chat
7. Verify it gets added in the proper alphabetical order in the LHN
8. Make sure you have draft chats
9. Verify the group of draft chats are sorted alphabetically in the LHN
10. Add a new draft to a new report

Expected Result:

Drafted message is moving to alphabetical order in the LHN after made drafted message

Actual Result:

User need to refresh the page in mWeb to make drafted message is moving to alphabetical order in the LHN

Workaround:

Unknow

Platform:

Where is this issue occurring?

• iOS
• Android
• Mobile Web

Version Number: 1.2.7.2

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5751003_Screen_Recording_20220926-213346_Chrome__1___1_.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[tgolen]

I think this is by design. We purposefully don't change the order of the active chat when adding drafts (to keep the LHN from jumping around, which can be jarring to the user).

[melvin-bot]

⚠️ Looks like this issue was linked to a possible regression on PRODUCTION here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.