Reporting on notes would be valuable for supporting the maintenance of a large scale knowledge base. Suggested fields include the following:
Note / header name
Parent header (if nested)
Created by
Created on
Last updated by
Last updated on (e.g. most recent version date)
Page views (last n days or months - TBD)
Example use case:
Create a list report of knowledge base notes sorted in descending order of "Last updated on" to gain quick insight into kb articles that could be stale and need to be reviewed and refreshed.
You can now run reports on documents to track information about your notes and whiteboards. Click Create new report, then select Documents as the record type for your report:
If there is additional metadata about documents that you would like to report on, please add a vote to this idea and comment what data you would like to have available: https://big.aha.io/ideas/A-I-15773. Thanks!
Hi - a key attribute for us to report on is Created By - currently we cannot report on this
Would also love to be able to report by status e.g. Draft, Pending Review, Approved, Review Due that sort of thing
We need this to report on NIHITO's and other activities within Aha.
I have exactly the same use case as Nora. I too am leading the effort to increase engagement with customers and demonstrate product research. My PMs also use Interview Snapshot Notes. I would like to be able to run a report to help pull out lists of the customer interviews.
We currently link the interviews to Contacts via URL - I have logged another 'Idea' to enable Notes to be included in Related tabs like all other items.
Looking forward to reporting on notes fields and note templates to get an overall view of data entered to support processes we implement for data points.
i am leading an effort at my company to enhance visibility into our product research. i am interested in having PMs document their customer interview notes in Aha. But I need to be able to reporting on notes, so need to be able to create and filter on them like I would other record types.
Example use case 2: I need to see all notes linked to me across workspaces (not just notes where I am the author).
So this would need an extra suggested field of "linked users" - I guess you could use "watchers" as a structured field more easily, that would have the same effect.