Add dedicated column for internal comments or notes in CSV export
C
Concrete Swordfish
Currently, the closest thing to an internal note is the Feedback column, which captures whatever the submitter typed.
There is no separate field that records why a writer closed or dismissed an item. That context lives only in Document360 itself, not in the export.
So when items are closed as irrelevant or testing-based, that reasoning is not captured in the CSV. The export only shows the end state (Status = Closed) with no indication of whether it was closed after resolution or disregarded intentionally.
If the reasoning behind closures is not recorded in the export, there is no audit trail distinguishing "addressed and closed" from "dismissed as irrelevant." That becomes a problem if someone reviews the data later and cannot tell the two apart.
Log In
I
Institutional Magpie
This is ultimately used to survey the KPI in which% of the cases feedback was resolved or rejected.
These figures can also indicate a problem for users that needs to be addressed elsewhere if there are several rejected feedback on the same topic, e.g. retrain user/readers or explain in an article why certain products or processes are not working as desired.