Alex Beaman
Alex Beaman
Nice, yeah agreed on all points haha. I wonder if anyone already started working on making `SubmitReport` 1:1:1?
Hey all 👋 this fixes a deploy blocker so it would be great to get some movement here - are we planning on a backend fix? Or is there a...
I spent a lot of time today fixing the backend, PR is up - but I didn't get to test your front end changes, sorry - if you can't find...
I definitely think it's fair to bump the bounty on this one, it's a pretty complicated issue that we're trying to get perfect 👍 @ntdiary are you waiting on me...
Cool, yeah @nkdengineer can now implement the correct sorting (with transaction `inserted` date - b/c that was just deployed yesterday) > and to see if https://github.com/Expensify/App/pull/52537#issuecomment-2504308501 should be fixed. I...
Ooh definitely agreed about tests 👍 though i wouldn't mind if that's in a follow-up just so we can get this out the door quicker 🤷
Ok IDK bout y'all, but I think y'all need to be suuuuuper clear on the setup you're using to confirm / deny if the policy owner is expected to be...
Thanks @ntdiary that's very helpful! Can you also please show what the approval workflow looks like? I see you mention "the final approver is policy owner (no.25)" but I would...
Thanks @ntdiary ! 👍 Ok ya so it IS expected that, in your case, the policy owner is the final approver - this is because the submitter's `submitsTo` is the...
Right, in @ntdiary 's case at least, it's not a backend bug, it is expected for the `submitsTo` to approve (in advanced approval case) AFTER all of the rule approvers