-
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
[$500] Request money - User A can request money in the workspace expense room using URL, even though only User B should be able to request money #27618
Comments
Job added to Upwork: https://www.upwork.com/jobs/~0193de23f043eea69d |
Triggered auto assignment to @JmillsExpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @zanyrenney ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan ( |
Seems not a bug as user B can request it from the workspace report |
There are two expense rooms, one for User A and the other for User B. In User B's expense room, the "Request Money" option is not available for User A, although you can still request money using a URL |
ProposalPlease re-state the problem that we are trying to solve in this issue.User A can request money in the workspace expense room using URL, even though only User B should be able to request money What is the root cause of that problem?In order to determine what report money type is available for a report, we normally use the getMoneyRequestOptions, like when getting options to display in the Compose + button here. But in the That's why even though user A does not have permission to request money in user B's workspace room, but still can workaround it by using the URL. What changes do you think we should make in order to solve the problem?We need to check that the user has permission to request money in Or we can use the canRequestMoney method directly. If the check return What alternative solutions did you explore? (Optional)This also happens for other screens, like split bill, we should fix it there too. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@JmillsExpensify, @situchan Eep! 4 days overdue now. Issues have feelings too... |
@JmillsExpensify, @situchan 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@JmillsExpensify @situchan this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@JmillsExpensify, @situchan 10 days overdue. I'm getting more depressed than Marvin. |
@JmillsExpensify, @situchan 12 days overdue. Walking. Toward. The. Light... |
@JmillsExpensify @situchan this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
This issue has not been updated in over 14 days. @JmillsExpensify, @situchan eroding to Weekly issue. |
@dukenv0307 is your proposal still valid? |
@situchan yes it is |
@JmillsExpensify @situchan this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:
Thanks! |
Current assignee @situchan is eligible for the Internal assigner, not assigning anyone new. |
@situchan thoughts on next steps and the existing proposals? |
Or should we keep this internal? |
No need to be internal yet. I will confirm today |
@JmillsExpensify, @situchan Eep! 4 days overdue now. Issues have feelings too... |
I think this was fixed in #23755. |
@situchan Yes, it's fixed since I added the check in |
Oh ok perfect! Ok so I'll issue payment for reporting and we're done here.
|
@ayazhussain79 I believe I've just sent you an offer in Upwork. Can you please accept. |
@JmillsExpensify offer accepted, Thank you |
All paid out. Thanks! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
User A should not be able to request money using the URL in workspace expense room, as it is intended only for User B
Actual Result:
User A can request money in the workspace expense room using URL, even though only User B should be able to request money
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.70-5
Reproducible in staging?: Yes
Reproducible in production?: Yes
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
screen-recording-2023-09-14-at-23702-am_JtSXgSJ7.mp4
Recording.40.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694642540255229
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: