Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.52k stars 2.87k forks source link

Admin doesn't have "Reject to submitter" report option in OldDot after taking control of report on WS with Instant Submit set #52043

Open garrettmknight opened 9 hours ago

garrettmknight commented 9 hours ago

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: N/A Reproducible in staging?: Y Reproducible in production?: Y 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: N/A Issue reported by: @saracouto Slack conversation (hyperlinked to channel name): #expense

Action Performed:

  1. Create an OldDot workspace, invite Submitter + Approver A, enable Advanced Approvals, set approval asl Submitter > Approver A
  2. As submitter, create expense in your WS chat and submit to Approver A
  3. As admin, open the report and take control

Expected Result:

The admin should see the option to Reject and when they click it they should have the Reject to submitter: option.

Actual Result:

The admin has the `Reject' button in OD, but that option doesn't populate with any sub-options.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

All

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

melvin-bot[bot] commented 9 hours 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.