Custom Metadata for adding reporting, analytics and filtering on articles
backlog
N
Nickel Reindeer
I would like the ability to add a metadata tag to an article that I can edit on a per article basis. As an example, for a known issue article, I would like to create a metadata tag called "Affected Versions" that I can edit on a per article basis as the value will depend on the specific issue. There are multiple other uses for metadata we can think of. We should be able to use these metadata tags in reports and analytics
Log In
N
Nickel Reindeer
Should these metadata tags be completely user-defined, or would you prefer a predefined set configurable by project admins?
I would like these tags to be defined by an admin at the project level. The tags should be global to all articles for that project.
Would you like the metadata field to support multiple values (e.g., multiple affected versions) or just one per tag?
They should support multiple values. As an example, we have an article for known issues and we want a tag called "Fixed In". The versions a issue can be fixed in is multiple and we will keep adding new versions.
Should these tags be visible to readers or only for internal use (e.g., reporting, filtering)?
Both.
How do you envision using these metadata tags in reports or analytics — for filtering, grouping, or trend analysis?
I can definitely see using these tags for filtering both in Advanced search, when the tags are public, and for filtering a list of articles.
D
D360 Product Management
marked this post as
backlog
Mohamed Shakheen
Hi Nickel Reindeer
Thanks for the detailed feedback. The idea of adding customizable metadata tags at the article level — such as “Affected Versions” for known issues — is very useful. It would provide more flexibility for content classification and open up stronger reporting and analytics capabilities.
To scope this effectively, could you confirm a few details?
- Should these metadata tags be completely user-defined, or would you prefer apredefined setconfigurable by project admins?
- Would you like the metadata field to support multiple values(e.g., multiple affected versions) or just one per tag?
- Should these tags be visible to readersor only forinternal use(e.g., reporting, filtering)?
- How do you envision using these metadata tags in reports or analytics— for filtering, grouping, or trend analysis?
Once we have this clarity, we can evaluate the implementation options and reporting integration.