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] Reports - "Hold" option doesn´t reappear on context menu after unapproving expense #61276
Version Number: 9.1.39-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers):ibellicotest+641@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome App Component: Money Requests
Action Performed:
Prerequisite: Delayed submissions and approvals enabled.
Open the staging.new.expensify.com website.
Open any workspace chat.
Submit a manual expense.
Tap on "Submit" and "Approve" on expense preview.
Navigate to "Reports"
Long tap on the just submitted expense and select it.
Tap on the dropdown menu.
Note that "Hold" option is not available.
Open the expense report and tap on the header.
Tap on "Unapprove"
Once redirected to expenses list again, select the same expense.
Tap on the dropdown menu.
Note that "Hold" option didn´t reappear.
Navigate to workspace chat again.
Long tap on expense preview.
Note that "Hold" option is available on context menu.
Expected Result:
"Hold" option should reappear between the expense´s options after unapproving it on "Reports" section.
Actual Result:
"Hold" option doesn´t reappear on expense´s options after unapproving it on "Reports"
👋 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.
@kadiealexander could you help process payment for @rushatgabhane and @ishakakkad? We closed their PR because the issue was fixed (probably as part of a duplicate issue). We should still process compensation since they worked on the PR and it was ready to be merged.
Activity
melvin-bot commentedon May 1, 2025
Triggered auto assignment to @kadiealexander (
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 May 1, 2025
Triggered auto assignment to @cead22 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 1, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 1, 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:
73 remaining items
ishakakkad commentedon Jun 16, 2025
@rushatgabhane PR is ready to review
rushatgabhane commentedon Jun 16, 2025
okayy, ty!!
luacmartins commentedon Jul 1, 2025
@kadiealexander could you help process payment for @rushatgabhane and @ishakakkad? We closed their PR because the issue was fixed (probably as part of a duplicate issue). We should still process compensation since they worked on the PR and it was ready to be merged.
kadiealexander commentedon Jul 2, 2025
Payments needed:
garrettmknight commentedon Jul 3, 2025
$500 approved for @rushatgabhane