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
👋 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.
Not a blocker, we just added the request money option in the workspace chat: #16670 @luacmartins do we need to update the tests in the testRail so Applause does not flag this as a bug?
@kbecciv this is being actively worked on as Part of the manual requests
This is behind beta so its ok the flow is not complete yet, i think we should wait for testrail changes until we finish most of the Mannual request project which will allow employees to submit expenses in the workspace chat.
I would close this issue in the meantime, there is no bug here
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
I would expect that there should be no request money option available.
Actual Result:
Workspace chat has Request money option with no attendees and Request button disabled
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.2.94.3
Reproducible in staging?: Yes
Reproducible in production?: No
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
Notes/Photos/Videos: Any additional supporting documentation
Bug6001278_video_78.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: