Open IuliiaHerets opened 1 week ago
Triggered auto assignment to @adelekennedy (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.
Triggered auto assignment to @tgolen (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
💬 A slack conversation has been started in #expensify-open-source
:wave: 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:
@luacmartins
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!
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: 9.0.66-0 Reproducible in staging?: Y Reproducible in production?: N Email or phone of affected tester (no customers): applausetester+29302390@applause.expensifail.com 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
https://github.com/user-attachments/assets/c08580d8-bf96-42fa-99f0-f4658920b18f
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @luacmartins