-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Workspace Feeds] Expensify Card - Reconciliation account link directs to hmm not here page #46108
Comments
Triggered auto assignment to @dangrous ( |
Triggered auto assignment to @adelekennedy ( |
👋 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:
|
Looks like a new page created in #45415 - pinging @koko57 @allgandalf @mountiny @MariaHCD |
This is still under beta, we can remove the blocker here |
Not a deploy blocker, we're still working on this project |
ah okay great! I'll remove the labels |
do you want me to assign y'all to this or will you handle as part of the implementation issues? |
Happy to take over to handle this |
I feel we can close this altogether, we really just want to uncomment the |
Do we need this issue then, @mountiny? |
@allgandalf I will make it weekly but I think its better to have this reminder than the comment in code |
yeah, I'll make sure we address this issue |
@koko57 is this ready to be worked on ? are we still waiting on |
Still waiting fot the BE |
What command are you waiting on? Is it |
yup! |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
After merging this PR #46978 this issue won't be reproducible |
@koko57 @mountiny @allgandalf this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
#46978 is merged, it can be retested now |
@m-natarajan can you please retest this in staging? |
Lets test and close this one @m-natarajan |
Closing as this should be fixed now, we can revisit if not |
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.11
Reproducible in staging?: y
Reproducible in production?: New feature
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:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Go to https://staging.new.expensify.com/home
Tap profile icon -- workspaces - workspace
Tap more features - enable expensify card
4 Tap expensify card
5.Tap settings -- settlement account
6.Tap Reconciliation account link
Expected Result:
Reconciliation account link must not direct to hmm not here page
Actual Result:
Reconciliation account link directs to hmm not here page
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6550970_1721767597287.Screenrecorder-2024-07-24-02-10-55-695_compress_1.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: