Skip to main content
New Idea

Freshdesk Reporting for "Service Desk Trends" completely inaccurate beyond 50 days on unresolved tickets

Related products:Freshdesk
  • January 25, 2024
  • 4 replies
  • 72 views

Forum|alt.badge.img+1

I opened a ticket and after a month was told that this does it by design.  Basically, if you try to generate a report that is more than 50 days, the “Unresolved ticket count” drops arbitrarily to zero.  If this is ‘by design’ maybe explain this.  This is the kind of graph that would set off false alarms for many casually reviewing the unresolved ticket count over time.

 

 

Support’s response after consulting three teams was this:

 

Our level 2 and developers teams have analysed the issue, and it was notified by our platform team that, currently, we are supporting a maximum of 50 data points in unresolved ticket metrics, and the 'grouping by date' filter will show only the last 50 days of data. The group can be changed to weekly or monthly to see more data. Apologies for the inconvenience caused and not being of much help here.

4 replies

Forum|alt.badge.img+3
  • Active Contributor
  • May 13, 2024

Also seeing this behaviour, would agree that if there is a filter for 90 days then you might expect that the system would be configured to display that level of detail.


Forum|alt.badge.img+1
  • Author
  • Active Contributor
  • May 23, 2024

Thanks, but I’d go a further and say that without any documentation, bulletins, warnings, or any other indicator that the system is limited to 50 days, there is every reason to expect that if you select the option for 90 days that the system would present 90 days of detail.


Forum|alt.badge.img+3
  • Active Contributor
  • May 28, 2024

seems that Fresh have “solved” the problem by removing the option for filtering by date… 

 

 


Thomas H
Top Contributor ⭐
Forum|alt.badge.img+2
  • Top Contributor ⭐
  • May 28, 2024

seems that Fresh have “solved” the problem by removing the option for filtering by date… 

 

 

I still do have the options and it still breaks after 50 datapoints.