Could you present your release notes in tables? That lets you use FM's
sort function to split the bugs into resolved and not. You just have to
have a column called something like "status" and then sort according to

Then immediately before release, you can split the table up to make your
3 sections and delete the status column. And I guess you could convert
to text if you can't use table layout in the final docs.

Cheers, Rebecca

>>> "Lin Surasky" <Lin.Surasky at> 05/19/07 5:43 AM >>>
Or can I keep my inflatable ducky hiked firmly around my middle and
paddle around in unstructured FM?

Over the past year or so, I've been poking around at structured FM with
no real goal in mind except to see if it might benefit us down the road.
For the most part, our process is pretty linear, and structured FM isn't
yet necessary for our regular user guides and manuals. So I have a
general idea of what we'd need, but I don't have the full picture yet...

I'm working on a new product with a new team, and each customer gets
their own version of the product with their own customized release
notes. When you all have stopped screaming, I'll continue... The release
notes are very simple. There are three main chapters: Requested Customer
Enhancements, Bug Fixes, and Known Issues (bugs that we're aware of that
have not yet been fixed). Please don't start screaming again; I really
need your advice! The gist of the situation is that on release day, I
have to go into our bug reporting system, and check all the Known Issues
to make sure they're still issues. If they've been fixed, they move to
the Bug Fixes section.

So I'm thinking that structured FM must be able to help, in that I could
somehow create element tags for Fixes and Issues, and then just change
the element tag for the Issues that have been fixed and somehow
regenerate the documents (how, I don't know -- do I need to maintain
this in a spreadsheet or database?) so that the content is moved to the
correct section along with its cross-referenced bullet (each section has
a bulleted list to make navigation easier). Oh yeah, and can they be
re-sorted by section into numerical order?

This sounds like it should be so simple, but I'm lost on the mechanics
-- any recommendations for how to set this up? Or if there's a better
way to manage this even in unstructured FM, that'd be great too. The
cutting and pasting is REALLY not my idea of fun!


You are currently subscribed to Framers as
rebecca.officer at

Send list messages to framers at

To unsubscribe send a blank email to
framers-unsubscribe at
or visit

Send administrative questions to listadmin at Visit for more resources and info.

NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesis Labs Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesis Labs.

Reply via email to