Hi, we've noticed this problem when launching KB support to our production customers. For us, the "There are no items in the selected series" message is confusing and suggests a bug instead of a missing feature. In my opinion this "Suggestion" issue touches:
1) must have / bug - missing details on upvoted articles - I'd expect either list of details as for all other KB report types (linked bug issue is resolved, but the problem remains). Looks to be what brought other recent commenters here as well
2) suggestions that would improve / redesign reporting (showing downvotes, article-focus instead of date-only focus)

I have just had this same exact issue brought to my attention in our environment.

I am currently on JSD DataCenter version 4.13.3

Clicking on any plotted point showing X number of Article Views returns "There are no items in the selected series" (See Attached) This is happening across all three of my environments (DEV, TEST, PROD)

Who is looking into this issue? I - and lots of others - need to see a solution to this bug!

Hi d16cf349799f,

Thanks for letting me know, and apologies for the inconvenience. The survey should now be accessible.

Thanks,
Raymond

The survey is not accessible (for me). Says I need to be in the owner's organization.

Hi everyone!

My name is Raymond, part of the JSM Product Management team. We’d love to find out more about our customer’s analytics and reporting needs. If you would like to share your thoughts, please fill out this short survey. Alternatively, please feel free to contact me at rcheng@atlassian.com.

I look forward to hearing from you!

Cheers,

Raymond

Hi paulo.ramalho,

Thank you for your feedback. I'm Raymond, a Product Manager with the JSM team. I’d love to have a conversation with you to find out more about your analytics and reporting requirements. If you are interested in having a chat, please reach out to me at rcheng@atlassian.com.

Cheers,
Raymond

It is unbelievable that Atlassian approved launching these reports while being incomplete.

Reports are useless if they are not actionable. How are we supposed to know which articles help users the most and which articles don't, so we can continuously improve our knowledge base?

With the recent focus on Jira Service Management, I'd expect to see this feature implemented, but it looks like it's been here for more than 3 years without any acknowledge from Atlassian.

Also, this is treated as a feature request. As we all know, very few feature requests actually make it to production, regardless of the amount of votes. In my honest opinion, this should be treated almost like a bug, because the current knowledge reports are actually useless and provide very little insight.

If the use case is not clear, I'm available for a chat with any Product people at Atlassian. Please do reach out if necessary.

This information also needs to be retrievable via an API. It's one thing to manually go in and look at this but we need to pull this data and perform analysis on the data.

Agree. Right now, it is not possible to learn and grow from this report.

We need to know the information, that is mentioned at the "Suggested Solution". AND which user deflected the article in order to get more feedback.