-
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
Expense - "Next step" message changes when requesting money offline #36510
Comments
👋 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:
|
Triggered auto assignment to @rlinoz ( |
We think that this bug might be related to #wave6 |
Hmm, I believe this should be happening in prod as well. Anyway, maybe @mountiny, @rezkiy37 or @allroundexperts can help. I think it is related to this PR: #34450, specifically this line: Line 876 in 63733d8
Because the next status is submitted we change the message to pending approval. |
ooh if this is happening in prod, let's call this NAB! Can you confirm @rlinoz ? 🙏 |
It is a regressing of this issue. I am going to take and fix this. |
Hi, I’m Michael (Mykhailo) from Callstack and I would like to work on this issue. |
@rezkiy37 I think GH failed to link the issue, do you mind linking it again? Also, do you happen to know if this is prod? If it is the PR I linked it is deployed, so this would not be a blocker. |
What's the linking do you mean? It already mentioned this issue - #28771. |
Oh I thought the bold issue in your comment was supposed to be a link, sorry. Great, so this seems to be deployed to production and we can the blocker label. |
This PR is already in production so not a blocker |
But please do continue with the fix just no need to CP @rezkiy37 |
I can confirm that it is deployed. So, it is not a blocker. Bug.mp4 |
Looks like I've found a root cause of the bug. Testing and opening a PR tomorrow. |
@thesahindia, let me clarify:
No, it is one of type of paid workspaces. You need to use OD for creating paid workspaces.
You need to use OD for managing paid workspaces. Does it make sense now? |
This issue has not been updated in over 15 days. @rlinoz, @rezkiy37 eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Hmmm this is in prod already, are we missing something? |
Yes, it is in prod - #36529 (comment). |
Yep, closing then |
Triggered auto assignment to @Christinadobrzyn ( |
Sorry about that @thesahindia @Christinadobrzyn , @thesahindia was the C+ reviewer for this issue, can you handle payment please? |
@Christinadobrzyn, we just need the payment summary here. Thanks! |
Gotcha! Payouts due:
@thesahindia you are paid in NewDot, right? Do we need a regression test here? |
I don't think this needs a specific test case but if we want here are the steps-
Feel free to close it. I will send the money request on NewDot. |
Created a regression test for QA to review if we need to add this - https://github.com/Expensify/Expensify/issues/386621 Payment summary here - #36510 (comment) going to close this out, feel free to reach out if I've missed anything! |
$500 approved for @thesahindia |
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: 1.4.41-3
Reproducible in staging?: Y
Reproducible in production?: N
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:
Precondition:
Expected Result:
The "Next step" message remains the same, which is "These expenses are scheduled to automatically submit later today!"
Actual Result:
The "Next step" message changes to "Waiting for x to approve these expenses."
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6379360_1707916650292.20240214_184640.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: