3 results found
-
Add a disclaimer to subscriber comments field
The subscriber comments field should have some kind of disclaimer in the myCSF front-end that reminds users that anything entered there will go into the final report. This disclaimer should only be visible if the user failed to opt-out of the associated preference. The suggestion here is to replace the "Comments:" label with "Comments (Note: Included in final report):".
5 votesNow that we offer the option to exclude subscriber comments from the final report, this suggestion is less critical than it once was.
-
Remove carriage returns or line breaks in all fields
In comments and other user input fields there are line breaks and carriage returns that cause multiple line comments to start on the second or third line instead of the first. This makes reports difficult to utlizie without expanding the row to see all the text.
3 votes -
Assessor Objects Should Have Same Reporting Capabilities as Assessed Organizations
As an assessor, we can create test objects. However, we don't have the ability to produce reports from those objects. Often, customers request analysis related to their specific assessments. Having the ability to "clone" their assessment and produce analytical reports is needed. For example, within the MyCSF portal, a customer can see the impact of changing factors has on the number of requirements. However, there is not a way to report on the specific requirements affected by the change in factors. Currently, providing this type of information for the customer is manual and time-consuming.
1 voteReporting from assessor demo environments was disabled intentionally.
- Don't see your idea?