Problem Statement
In mobile apps (including gaming) customers usually don't update their apps immediately.
So what happens a developer has fixed an issue, marks it as resolved in release upcoming.
But the events are still coming in, which is a waste of resources for both customer as Sentry.
Solution Brainstorm
Ideally it should just filter out the issues once it's resolved in next release. Or give a project config that can do that so that the noise and consumption reduces.
This won't make sense for marking it resolved, only for marking it resolved in next release
Product Area
Issues