Wrong dates (firstSeen, lastSeen, ...)

[raulparada]

What happened:
Using this datasource to create a basic table displaying our top issues. Noticed that all the 'firstSeen' of the issues were extremely recent, and after comparing with Sentry's info (on their UI) and noticing it's wrong, and a little further digging realised it's being influenced by the date range selected (Grafana's selector top-right for all clarity, not in query.). Every time I adapt the range of the query, this information changes for the same issues.

What you expected to happen:
I'd expect 'firstSeen' of an issue to be what's reported on Sentry's UI (i.e. the moment the issue was first seen ever), even if (as usual) outside the query range and not be influenced by this range. For all clarity, I expect date range to impact other fields, such as:

• count
• userCount
• ...maybe others

...but not this. This is extremely misleading as—to us at least—the 'firstSeen' of an issue is usually the initial bit of information to drive an investigation, by correlating it to a release/deployment. I could understand some few users having a different need that aligns with current behaviour, but IMO in that case those fields should be named differently (e.g. firstSeenRange or so)

How to reproduce it (as minimally and precisely as possible):

1. Use this plugin to create a table (or anything else that allows visualising these dates info)
2. Play with the Grafana date query selector
3. Notice how the date fields change for the exact same issues

Screenshots

Anything else we need to know?:
A same/similar issue was already reported on #168 but closed due to inactivity. I would just like to point out that such a bug probably makes the usage of the plugin a net negative due to misleading info, so please please don't disregard again 🙏

Environment:

• Grafana version: 12.0.0
• Plugin version: 2.2.1
• OS Grafana is installed on: (?) Self-hosted
• User OS & Browser: macOS / Chrome
• Others: