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
[$500] Hold Request - Composer is focused while RHP is open #36829
Version Number: 1.4.43-0 Reproducible in staging?: y Reproducible in production?: new feature 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: applause internal team Slack conversation:
Action Performed:
Sign up with a new account
Create an IOU with a user
Navigate to IOU reports details page
Click on three dot › Hold request > enter reason › press enter
Expected Result:
Composer shouldn't be focused
Actual Result:
Composer is focused
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]Hold Request - Composer is focused while RHP is open[/-][+][$500] Hold Request - Composer is focused while RHP is open[/+]on Feb 20, 2024
👋 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.
Please re-state the problem that we are trying to solve in this issue.
The Git it button is not focused
What is the root cause of that problem?
On the 1st screen, "Hold Request", when the button "Hold Request" is clicked, there's an actiopn to turn back to the main request report screen, wish bring back focus to the "Write anything..' input
Activity
[-]Hold Request - Composer is focused while RHP is open[/-][+][$500] Hold Request - Composer is focused while RHP is open[/+]melvin-bot commentedon Feb 20, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01d88b69191153c8ff
melvin-bot commentedon Feb 20, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (
External)melvin-bot commentedon Feb 20, 2024
Triggered auto assignment to @dylanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.github-actions commentedon Feb 20, 2024
👋 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 Feb 20, 2024
Triggered auto assignment to @MonilBhavsar (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.kavimuru commentedon Feb 20, 2024
We think this bug might be related to #vip-bills
cc @davidcardoza
rushatgabhane commentedon Feb 20, 2024
is this severe enough to be deploy blocker?
MonilBhavsar commentedon Feb 20, 2024
Agree, we can remove deploy blocker as it is not critical.
Commented on the PR it is coming from #33897 (comment)
dragnoir commentedon Feb 20, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
The Git it button is not focused
What is the root cause of that problem?
On the 1st screen, "Hold Request", when the button "Hold Request" is clicked, there's an actiopn to turn back to the main request report screen, wish bring back focus to the "Write anything..' input
App/src/pages/iou/HoldReasonPage.tsx
Lines 42 to 49 in 0f372c2
The navigate back function turn to the main report screen and does not open the next "This request is on Hold" screen.
What changes do you think we should make in order to solve the problem?
When the screen "This request is on Hold" is opened we need to set the focus on the "Got it" button on src/pages/ProcessMoneyRequestHoldPage.tsx
POC:
20240220_101333.mp4
dylanexpensify commentedon Feb 20, 2024
@rushatgabhane to review proposal!
MonilBhavsar commentedon Feb 20, 2024
Should this be handled as regression as it coming from #33897 that was deployed last night?
BartoszGrajdek commentedon Feb 20, 2024
This issue is a duplicate of #36825 - after we fix the original issue this won't be a problem anymore
robertjchen commentedon Feb 20, 2024
Closing, to be handled in #36825