Remove 1 year time bound limitation on the vulnerability over time chart

The ES query on the vulnerabilities over time chart is time bounded for the last 1 year. This time bound limitation was applied for performance reasons as we have 1 year as the retention time period for vulnerabilities.

But we are receiving customer feedback (zendesk ticket) about the counts inaccuracy across various charts and reports.

Proposal

Remove this time bound limit applied on the query as the retention policy is not fully enabled and can take a longer time to roll out.

Remove the time range condition { "range": { "created_at": { "_name": "filters:range:created_at", "gte": "2024-11-19", "lte": "2025-11-19" } } } from the query filter:

{ "query": { "bool": { "filter": [ { "bool": { "should": [ { "prefix": { "traversal_ids": { "_name": "namespace:ancestry_filter:descendants", "value": "110-" } } } ], "minimum_should_match": 1 } }, { "range": { "created_at": { "_name": "filters:range:created_at", "gte": "2024-11-19", "lte": "2025-11-19" } } }, { "term": { "archived": { "_name": "filters:archived_projects", "value": false } } }, { "terms": { "_name": "filters:severity", "severity": [ 1, 2, 4, 5, 6, 7 ] } } ] } }, "size": 0, "aggs": { "open_by_day": { "filters": { "filters": { "2025-10-20": { "bool": { "must": [ { "range": { "created_at": { "lte": "2025-10-20T23:59:59Z" } } } ], "must_not": [ { "range": { "resolved_at": { "lte": "2025-10-20T23:59:59Z" } } }, ...