-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[Due for payment 2025-02-27] [$250] Up and down arrows not working in the composer sometimes #55734
Comments
Triggered auto assignment to @muttmuure ( |
Hello, here is the PR with the fix |
Job added to Upwork: https://www.upwork.com/jobs/~021882813733020527368 |
Current assignee @dominictb is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to @jliexpensify ( |
It looks like @Skalakid needs to address comments in the PR. No action from B0 yet. |
Removed Looks like progress is being made on the PR the past few days, let try to wrap this one up (while also knowing that this is real "Sorry, had to finish some tasks with higher priority. Looking into this right now) |
Hello, the PR is finished, approved by C+, and now I'm waiting for the review from an internal |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.2-1 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-02-27. 🎊 For reference, here are some details about the assignees on this issue:
|
@dominictb @jliexpensify @dominictb 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] |
Payment Summary
|
Bumping @dominictb for a checklist |
on it now |
BugZero Checklist:
Bug classificationSource of bug:
Where bug was reported:
Who reported the bug:
Regression Test ProposalTest:
Do we agree 👍 or 👎 |
Payment Summary
BugZero Checklist (@jliexpensify)
|
Paid and job closed! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number:
Reproducible in staging?:
Reproducible in production?:
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 @mallenexpensify
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C049HHMV9SM/p1737670596476479
Action Performed:
Break down in numbered steps
Expected Result:
Describe what you think should've happened
You should be able to move the cursor within the message
Actual Result:
Describe what actually happened
Unable to move through the composed message
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @jliexpensifyThe text was updated successfully, but these errors were encountered: