Feature Request
Simplified issue resolution
MarcoB
I recently migrated from App Center to Raygun for our mobile app. After investigating some crash reports and committing a fix, I marked them as Resolved. A couple of days later, I found that the errors I Resolved were Active again.
I turns out that Raygun will change the state back to Active if the error happens again after it's set as "Resolved". A dedicated "Resolved in version" allows specifying which version the issue was fixed in.
This is problematic for me as I don't know which version will contain the fix at the time I commit my changes. I just want that error to no longer appear in Raygun as it no longer needs my attention. I only want to see the unresolved issues.
There are workarounds, but they're cumbresome. I could:
- Ignore the error: I would have to set an arbitrarily high number of repetitions or time so that it's not re-opened. Then, after deploying the update I would have to go to the "Ignored" tab, change the item state to "Resolved in version" and enter the version.
- Permanently Ignore the error: As before, I would have to remember, after deploying an update, to go to the "Permanently ignored" tab, change state to "Resolved in version" and enter the version.
This would repeat for each error I fix. In both cases, there will be other items in those tabs, so I'd have to manually find which items need changing state.
In contrast, in App Center you would simply mark an item as fixed and it would automatically ignore any new report from that version. But if it happened on any other version, it would still pop up. It was straightforward.
I would like Raygun to automatically ignore future reports of a Resolved error if it happens on the same version. Or at least to have an option in the settings to enable this behaviour.
Raygun
John-Daniel Trask
Posted on
Jul 14 2025
We will mull on this to make it easier.
Though, speaking openly, I think App Center pretending an active error isn't occuring anymore in the version that's out there is simply misleading users of App Center. I could see our customers with large teams being very confused why Raygun is not showing ongoing active error reports in a version where the error is known to occur.
Hence we need to think of how to handle this in a better way than we do now, or that App Center tried to put in. Like "Resolved in next version", and leveraged our existing "Resolved in version" workflow (to bump back to Active if it occurs again in a future version).
Reporting as Resolved in versions where the bug is actually still an active bug would also distort our Versions report that shows what active issues, reoccuring, etc occured in a version. Pretending they're fixed when not would mislead a lot of our customers.