You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-10-17] Chat - Composer is not focused after sending text with image #72142
Version Number: 9.2.28-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#69523 Email or phone of affected tester (no customers):sdijsnoisjnosij@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Chat Report View
Action Performed:
Go to staging.new.expensify.com
Copy an image.
Go to any chat.
Type anything on the composer.
Paste the image via CMD + V.
Click Send or hit Enter.
Expected Result:
Composer will be focused after sending text with image.
Actual Result:
Composer is not focused after sending text with image.
👋 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:
Identify the pull request that introduced this issue and revert it.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.28-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@parasharrajat@mallenexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
The parent issue is a tracking issue of the major refactor of many pages. So payment will be handled once that is completed. This is a side effect of one of the PRs, so I expect no payment here.
Activity
melvin-bot commentedon Oct 8, 2025
Triggered auto assignment to @mallenexpensify (
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.melvin-bot commentedon Oct 8, 2025
Triggered auto assignment to @AndrewGable (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Oct 8, 2025
👋 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:
melvin-bot commentedon Oct 8, 2025
💬 A slack conversation has been started in #expensify-open-source
17 remaining items
melvin-bot commentedon Oct 10, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.28-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-10-17. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 10, 2025
@parasharrajat @mallenexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
melvin-bot commentedon Oct 17, 2025
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 18, 2025
Is this from a regression?
AttachmentModalScreen#69523I see it linked in the OP, unsure if payment is due to @parasharrajat
parasharrajat commentedon Oct 18, 2025
No payment here.
mallenexpensify commentedon Oct 20, 2025
Is that cuz of a regression? If so, was that issue paid out at 50% @parasharrajat ?
parasharrajat commentedon Oct 21, 2025
The parent issue is a tracking issue of the major refactor of many pages. So payment will be handled once that is completed. This is a side effect of one of the PRs, so I expect no payment here.
mallenexpensify commentedon Oct 21, 2025
Thanks @parasharrajat, closing