How can we craft patch notes that are clear for non-technical users?

[MarkQR]

I'm a project manager for a mid-sized SaaS platform, and our team is struggling to write clear, user-friendly patch notes that effectively communicate both bug fixes and new features to our non-technical customer base without causing confusion or support tickets. Our current notes are too jargon-heavy and simply list JIRA ticket numbers, which leads to users missing important changes or asking what a fix actually means for their workflow. For other product teams, what process or template do you use to draft and review patch notes? How do you balance technical accuracy with accessibility, and do you involve customer support or marketing early in the drafting process to ensure the notes answer the right questions?