-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Search - Pay button does not appear on the expense after the duplicates are sorted #53023
Comments
Triggered auto assignment to @adelekennedy ( |
Triggered auto assignment to @tgolen ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
This is a BE bug. The backend doesn't update a new value for action field |
this is specific flow and the pay button appears after refreshing or navigating away and back so I dont think this has to be a blocker for the deploy as the user is not blocked from taking the action they want to |
I'll work on this since my PR introduced the feature |
@luacmartins, @adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Working on it this week |
This seems to be fixed. Closing. Screen.Recording.2024-12-04.at.2.22.20.PM.mov |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.66-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
Pay button should appear on the expense because the duplicates are sorted and Pay button also appears on the expense RHP.
Actual Result:
Pay button does not appear on the expense after the duplicates are sorted.
It only appears after the page is refreshed.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Screenshots/Videos
Bug6674000_1732356224342.20241123_174735.1.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @luacmartinsThe text was updated successfully, but these errors were encountered: