You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, After the 4.1.2 Upgrade it seems that on dashboards any graph with customFields do not display properly anymore:
Graph settings:
All other graphs are working as expected, however all customFields graphs are defaulting to "1" for graph results, if I click on the graph it clearly shows there are more than 1 result.
This bug started with 4.1.2 for us, graphs have not been changed and where working perfectly fine before. We also tried creating new graphs in the hopes that this would solve it, however the same thing appears.
The number in the middle shows the correct number of results based on what we have found. The bug is only presents on the chart around it.
The same bug is present on two different systems.
Steps to Reproduce
Create a donut dashboard with a aggregation on a customFields. The problem should appear. I am not sure if this is only the donut which is affected or if others are affected aswell. We mainly use donuts.
The text was updated successfully, but these errors were encountered:
Request Type
Bug
Work Environment
Problem Description
Hi, After the 4.1.2 Upgrade it seems that on dashboards any graph with customFields do not display properly anymore:


Graph settings:
All other graphs are working as expected, however all customFields graphs are defaulting to "1" for graph results, if I click on the graph it clearly shows there are more than 1 result.
This bug started with 4.1.2 for us, graphs have not been changed and where working perfectly fine before. We also tried creating new graphs in the hopes that this would solve it, however the same thing appears.
The number in the middle shows the correct number of results based on what we have found. The bug is only presents on the chart around it.
The same bug is present on two different systems.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: