Question: Fix for #7651 closed issue - not seeing fixed results

[mickster1963]

How can we help?

Please share briefly:
Opened issue #7651 with advanced reporting issues. 7651 was close as being resolved. I have been expecting a new release to resolve(assumption local side code) the issue but have not seen one. Otherwise issue does still exist and wasn't clear on what expectations I would see to resolve or actionables on my part.

Please advise of actions I should take to resolve. Thank you very much.

--Mickey A.

[github-actions]

Thanks for the question!

To help us answer quickly, please include:

• What you're trying to do: Your goal or workflow
• What you've tried: Steps or settings you've attempted
• Expected behavior: What you expected to happen

Need to attach system details? If you're an admin:

👉 Admin → System Maintenance → System Logs (or click the debug icon)

Attach logs or screenshots if helpful. Please redact any private information.

Screenshots help: A quick image can clarify your question.

Advanced users: If this is a UI flow you can reproduce, the Cypress Recorder helps. Capture the steps and attach an exported spec.

👉 Bug Reporting & Diagnostics Guide

---

Note: ChurchCRM is maintained by volunteers. While we try to respond to every question quickly, there may be a delay in our response depending on availability. Thanks for asking! 🙂

[DawoudIO]

I plan to release 6.3.0 today and that will have the fix

[DawoudIO]

https://github.com/ChurchCRM/CRM/releases/tag/6.3.0 has been released