Loading...
Loading...
When you have a breakdown exclusion defined for two breakdowns that are also used in a breakdown relation, the AnalyticsHub breakdown panel will generate repeated element labels for the "invalid" breakdown relation. Steps to Reproduce 1. Create two breakdown sources: - Parent department - Department 2. For each breakdown add a mapping from incident table through business_service: business_service.department and business_service.department.parent 3. Create a breakdown relation from department to parent department and give parent as the common field. 5. Create breakdown exclusion between parent department and department breakdowns. 6. Add department, parent department, and one other breakdown to indicator number of new incidents and remove all other breakdowns that are not required. 7. Add update the departments table so some departments have a parent department. 8. Add some departments to business services. 9. Add some new incidents to the incident table with business services that you have updated, so that they can be picked up by data collection. 10. Remove all indicators except number of new incidents from the incident historic data collection job. 11. Run the job. 12. When completed, go to the detailed scorecard. Select any parent department for level 1 breakdown, followed by the other breakdown that is not department. By default the related department breakdown will be chosen and you will see unexpected results.
After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience. As a workaround, remove the breakdown exclusion if you want to use the breakdown relation.
PRB1334575
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.