-
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
[$250] Expense - Submit expense option is not disabled for users who are invited to expense report #46340
Comments
Triggered auto assignment to @OfstadC ( |
@OfstadC FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #wave-collect - Release 1 |
Edited by proposal-police: This proposal was edited at 2023-10-21T22:06:00Z. ProposalPlease re-state the problem that we are trying to solve in this issue.Submit expense option is not disabled for the users who are invited to the expense report What is the root cause of that problem?For the iou report, the policy is the personal policy of the user so Lines 1604 to 1608 in 5e65276
When we submit an expense, we get the Line 7315 in 5e65276
For the expense report, the invited user doesn't have the policy data of the expense report, and Line 6123 in 87c116b
What changes do you think we should make in order to solve the problem?We should check if the user can not access the parent report we will return
Lines 1604 to 1608 in 5e65276
What alternative solutions did you explore? (Optional)Or we can check for iou report that will return false if the current user is not the manager and is not the owner of the iou report
Lines 1604 to 1608 in 5e65276
For the expense report, we can add the check
Line 6123 in 87c116b
or we can add a case in |
Assigned to me while I was OoO - reassigning |
Triggered auto assignment to @zanyrenney ( |
The desired v expected behaviour is a bit odd. I am not sure what the exact behaviour should be here as this seems like a pretty niche use case. Going to keep investigating in the collect room. |
Is the reason that there should be disabled, that they are being invited to an expense report of another user? That's the only case I can see that they should be and from submitting an expense on someone else's expense report? But I'm not clear on this otherwise. @lanitochka17 please can you confirm or add to the OP a bit more detail about the specific use case you are testing for. Thanks! |
Bump @lanitochka17 |
Issue was found running the TC https://expensify.testrail.io/index.php?/tests/view/4771930 |
Thank you! |
Adding |
Job added to Upwork: https://www.upwork.com/jobs/~01966947a9e891013b |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 ( |
@nkdengineer's proposal LGTM 🎀👀🎀 C+ reviewed |
📣 @dukenv0307 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@dukenv0307 we have a follow PR here, please take a look |
This issue has not been updated in over 15 days. @zanyrenney, @aldo-expensify, @dukenv0307, @nkdengineer 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! |
@zanyrenney The Issue was deployed to production 1 month ago. Should we process payment here |
The payment summary would be: @dukenv0307 in C+ role: $250 Correct? |
@aldo-expensify I agree |
1 similar comment
@aldo-expensify I agree |
payment summary @dukenv0307 in C+ role: $250 paid via upwork |
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.13-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4771930
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Submit expense option should be disabled for the users who are invited to the expense rep
Actual Result:
Submit expense option is not disabled for the users who are invited to the expense report
Invited user can go through the flow but blocked at the confirmation page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6553848_1722011341978.20240727_002330.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @zanyrenneyThe text was updated successfully, but these errors were encountered: