I'm using the ordinary Issues element for questions and answers from my customers.
Put them into a Questions folder.
The issue name is the question (may be as long, as 110 char in three rows).
The answers I put into the note. If I got the answer, I change the status from proposed to the Approved, that changes the left sided column from yellow to blue.
I put these "Question" issues onto the requirements folder. If I got an answer, and think this is a requirement, I create a Requirement element, name it as requirement text, and add note as needed. Then create Realization dependency from the Requirement to the question.
I can color the requriements differently from the questions, to get a better look. For examle all requirements are pinks, all questions all yelows
If I create an rtf documentation on the question folder, that shows only the issues and object name, then I get all the questions, and answer, that I can send to my customers as needed.
If I create an Implementation documentation (Project/Documentatio/Implementation details...) on the question folder, I get all the questions, that became a requirement. If I create a dependency documentation on the requirement folder (Project/Documentatio/Dependency details...), I get, wich questions comprises the base of the requirements.
If I watch the requirement diagram, I visually see, how the questions are releated to requirements, and wich questions are answered, and wich of them not.
I can connect the question to any element, in any folder.
Morover, I can create subfolders for questions for speciale cases.
I can create rtf document for questions, created/modfied after selected date, so I can mail only the new questions to my customers.
This method works well for me.
Gabor
