Better grouping of Issues #31
Description
Problem
I use the Open Subtitles plugin in Emby (in addition to using Bazarr, yeah, probably overkill) and a lot of the errors I am getting logged in my Issues tab are the same thing over and over, but with slightly different strings in the error message. This doesn't really impact just people using Emby and the Open Subtitles plugin, but I feel demonstrates the issue pretty well.
For example, the following are in my Issues tab as separate, but are really the same underlying issue:
502 BadGateway Response from https://api.opensubtitles.com/api/v1/subtitles?episode_number=18&imdb_id=72562&languages=en&moviehash=144bc7431edfab60&query=Saturday Night Live - s24e18 - Cuba Gooding Jr.+Ricky Martin.mkv&season_number=24
502 BadGateway Response from https://api.opensubtitles.com/api/v1/subtitles?episode_number=6&imdb_id=72562&languages=en&moviehash=262820ea96c09ce4&query=Saturday Night Live - s28e06 - Brittany Murphy+Nelly.mkv&season_number=28
502 BadGateway Response from https://api.opensubtitles.com/api/v1/subtitles?episode_number=20&imdb_id=72562&languages=en&moviehash=60fe8b390b4d7abc&query=Saturday Night Live - s14e20 - Steve Martin+Tom Petty and the Heartbreakers.mkv&season_number=14
These are all getting logged because something broken down when trying to fetch subtitles. But they are all the same issue, and I feel should be getting grouped so I can just mark them as Ignored/Resolved/etc. at once.
Proposed Solution
I believe that when items land in the Issues tab, it's grouping multiple found logs by matching on the full string of the error message. I suggest it may be better if you could recognize elements of these errors that might change, particularly URLs. So in my example above, you'd really just need to look for this when matching whether the issues should be grouped:
502 BadGateway Response from https://api.opensubtitles.com/
Everything after the URL could change, but just this info above should be enough to be an indicator of what the issue is, and I shouldn't need dozens of separate Issues logged for this that I have to Ignore/Resolve individually.
Alternatives Considered
If this can't be done easily enough, maybe implement a way we can multi-select Issues and perform actions on all of them at once.
Feature Area
Issue Tracking
Priority
Nice to have
Additional Context
No response