We at Prism Defence are a customer of Requirements Yogi, and this issue is a critical priority for our team. It directly impacts our ability to export key deliverables, such as Stakeholder Requirements Specifications, which are essential for our project deadlines and client commitments. Resolving this issue is crucial for maintaining our workflow and ensuring timely delivery of these important documents.

This issue is in our backlog. We cannot provide an ETA.

Hey team,
We are getting back to you on this issue that is still not solved for our customers.
One of our customers (as you can see in the other comments) is deeply impacted by this issue as they absolutely need this feature to work for their reporting needs.
The above issue has not evolved and the customer, or us, have not received updates.
Could you let us know if you had any more news for this ticket ?
Thank you.
Best regards
Mileva Briand
Head of Customer Support @ Requirement Yogi Silver Marketplace Partner

3fc9a08d5c87 can I get some sort of response to this issue, at least an acknowledgement that it is indeed something for Atalassian to fix, rather than the Requirements Yogi macro vendor, please.  This is becoming increasingly critical to HERE.

3fc9a08d5c87, I've seen no activity (though I don't have access to the page mentioned above) on this issue.  

Being able to export Confluence pages with the RY Report macro output visible is critical to our use of Confluence for this project.  This is how we expose our documentation to our customers.  The HTML export is the highest priority.

It also seems like a fairly unfundamental requirement for content generating macros in general, otherwise why offer these exports at all?

Thanks

Drew

Note (this is the original customer logging the RY issue), this affects specifically the Requirements Yogi "Report" macro that generates a table output.  And it affects Word, PDF and HTLM exports.  

There RY macros output does appear in the Confluence Exports.