-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
non-admin approvers are removed from a report when it is retracted #46913
Comments
Triggered auto assignment to @adelekennedy ( |
still waiting for an internal pick up |
Triggered auto assignment to @blimpich, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@mollfpr C+ reviewed the PR linked to this issue. @ishpaul777 did you link the right issue? |
Not sure why Melvin auto-assigned me to this. Can't pick this up right now. |
@blimpich I think the |
@aldo-expensify It didn't use to, is that a recent change we made? Isn't that just a re-hash of the |
I just removed and re-added the My guess is this might be a bug related to the related PR trying to find an internal engineer to review this PR. That would make more sense since labels were all applied days ago but that melvin comment on the PR lines up exactly to the minute I was assigned to this. I'm pretty sure we only auto-assign internal engineers for issues tagged |
Ahhh, maybe you are right and |
Assigning them since I believe they need to be paid |
This is ready for payment! 🎉 |
I believe we also need to update the back-end to not remove the approvers from the report when it is retracted, is that right? |
i guess that should not hold payment, right ? |
agreed - I think we can move forward with payment here |
Payouts due:
|
I accepted offer on upwork, I guess @mollfpr get paid through Newdot |
@mollfpr, @adelekennedy, @ishpaul777 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@puneetlath payment is made here but do we need to keep this open until an engineer will pick up the back-end update or is that being worked on elsewhere? |
I'm not aware of it being elsewhere. You can create a separate issue if you think that's easier to manage. |
$250 approved for @mollfpr |
@mollfpr, @adelekennedy, @ishpaul777 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@adelekennedy created BE issue here to track in wave-control. |
new issue is created this is good to close : |
Thanks everyone. |
Is there missing piece of the workspace setup here? I picked up https://github.com/Expensify/Expensify/issues/428467 which should ostensibly have the same reproduction steps as this one, but I don't seem to be have the option to retract the report in OldDot as the submitter. |
You should be able to retract it as long as it hasn't been approved yet. Can you show a screenshot of what you see? |
Ah, the missing piece was that instant submit was on. I am now able to reproduce this and will figure out why it is happening and fix it. |
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.17-0
Reproducible in staging?: y
Reproducible in production?: y
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: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722958568843569
Action Performed:
Expected Result:
Should have access to the report
Actual Result:
hmm it is not here page appears
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Recording.421.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: