Hi, can I take a shot at this? :)

@nadineah you already have #3426 assigned - do you want both? Or would you rather focus on one at a time?

@dorner My bad, one at a time would be better

Hello, I would like to contribute in this issue and try my best to solve this!
Thank You.

Give it a go!

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.

Automatically unassigned after 7 days of inactivity.

@dorner Please assign me this issue again, Thank You!

May I work on this one?

Please do.

Given that the existing PR is incomplete, has a number of unresolved issues, and is far behind main, would it be appropriate to start with a fresh branch and PR? What is the recommended course of action in this case?

Oh yes, please. IIRC, they were going down a wrong road.

Is the field Organization.email the bank’s contact email the details are referring to? The consideration that this may be a role based feature makes me suspect that the contact email is instead a user’s email.

Also, there is already the RequestsConfirmationMailer set up to send a confirmation email to the partner and user making the request when a request is made. Should I simply modify RequestsConfirmationMailer to satisfy this issue (CC the organization if they have opted in) or create a separate mailer that emails exclusively the organization?

Yes it is.
For background - this is mainly to benefit banks that are relatively small, and won't be in the system every day anyway. They do, however, monitor an email.

I think you could modify the existing mailer. This email is prompted by the same thing, so it makes sense to me.

This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned.