Preserve "Status" macros in reports
In our system, 'Status' macros are commonly used to indicate he progress of requirements. In RY-reports, these get flattened out as plain text, losing the valuable color information.
Since some other markup (e.g. images) are correctly preserved, I would hope that this is possible for simple macros like 'Status' as well. (Possibly others as well? The more the better!)
Thanks for the hint! This solution is good enough for us.
Great for the first half of your comment, less great for the second half. The other way to reindex a page is to click the " ... " menu on the top-right of the page (formerly named the "Tools" menu), and click on Requirement Yogi:
Clicking "Refresh requirement descriptions" on that page updates the excerpts.
I notice it's not very easy for you.
You can also go to the database and set "AO_32F7CE_AOREQUIREMENT"."HTMLFLAG" to 1, so requirements are updated the next time the page is viewed.
I'm planning another release for this week. Do you want that include a feature to make it easier for you?
Just updated to 1.9.0 and it seems to work fine. However: existing requirements do not seem to be updated to reflect this preservation of formatting. I would have to go through all pages, make an actual modification to each requirement. Is there any easier way to update the database?
Our use case is to produce exportable self-contained documents that we can provide to external suppliers without access to our confluence system. Admittedly, this use case stretches the RY-report macro to its limits, but I have not yet found any other approach to realize this.
I have designed RY to render in all of those places, It displays correctly (ok, it displays "as designed", which is more limited) because it doesn't need any CSS/JS (stylesheets) dependency. It wouldn't be as easy if I displayed "rich text".
Honestly, RY was more designed to keep the title of the requirement and leave the details in the original page. The status macro is a bit special because it can also be used as a colorful way to show the status of a requirement, but I recommend keeping it simple and letting the user come back to the original page when needed.