Hi Soojeong. Wanted to double check that you’re sure these were functioning links before the upgrade? We’ve had longstanding inconsistencies with which of our categories are drillable due to old technical limitations.
You mentioned that “We’ve had longstanding inconsistencies with which of our categories are drillable due to old technical limitations.”
I would like to understand this in more detail.
Could you please clarify:
What specific technical limitations are being referred to?
Is this the same issue as the behavior we are currently observing?
The “longstanding technical limitations” in play with some of these constraints are not insurmountable, but rather relate to the lack of well optimized indexing and presentation of the data in question.
So for instance, one explanation for this screenshot would be if you’re looking at portfolio security reports - we do not store, and (as far as I know) have never stored, lists of hotspots at the portfolio level, so there’s nowhere that such a link could point to without incurring serious performance penalties on some servers.
(If you’re interested, we’re worried mostly about portfolios with 1000+ projects that are all being actively developed - poorly optimized operations in that scenario can be painfully slow)
So that’s why I’d like to know whether this is
(a) on the projects page, where such links could hypothetically exist, and
(b) if so, did those links actually exist on a previous version?
The issue is not occurring in Portfolios.
It occurs only in Security Hotspots within the Security Reports of a specific project.
This issue did not occur in the previous version.