"New Email" recipient not auto-populated on proposal doctypes

[harshtandiya]

Summary

When clicking "New Email" on an Event Proposal (and other proposal doctypes), the recipient ("To") field does not auto-populate, so the user has to manually copy-paste the email address every time.

When I click on new email in event proposal doctype, the email to field doesn't auto populate ... why do I need to manually copy paste email each time in buzz when I want to send a mail?

Root cause

None of the proposal doctypes expose an email/contact field on the parent, so Frappe's "New Email" dialog has nothing to prefill the recipient from:

• Talk Proposal — no email field on the parent. Emails live only on the Proposal Speaker child table (email field) and via submitted_by (Link to User).
• Event Proposal — no email/contact field at all (only host Link and host_company Data).
• Sponsorship Enquiry — no email field; it sends mail using recipients=[self.owner].

All three have the email permission flag enabled, which is why the "New Email" action appears — but there is no field for the recipient to be sourced from.

Suggested approach

Surface a contact email on the parent doctype so the communication dialog can prefill it. Options:

• Add a contact_email (Data/Email) field, fetched from submitted_by (or the primary speaker) on Talk Proposal, and an equivalent on Event Proposal / Sponsorship Enquiry.
• Alternatively wire up the doctype's sender/recipient defaults (e.g. sender_field / contact link) so Frappe's email dialog resolves the "To" automatically.

Decision needed on which field should drive the recipient for each doctype.

Affected files

• buzz/proposals/doctype/event_proposal/event_proposal.json / .py
• buzz/proposals/doctype/talk_proposal/talk_proposal.json / .py
• buzz/proposals/doctype/proposal_speaker/proposal_speaker.json (email field lives here)
• buzz/proposals/doctype/sponsorship_enquiry/sponsorship_enquiry.json / .py

[harshtandiya]

Moving to V2