OPEN Problem Reports catalogue [as of 26 May 2026]

0xFeedBeef

This is a work in progress, so treat it as such!

The intention is to have a single catalogue of open problems (and potential solutions) so both the devs and users can see those and cross-reference. This is not a feature request or suggestions catalogue, there’s already a sticky for that.

Problem reports (PRs) should (will?) be added here after they are reported in a general forum post and confirmed by another user. Before posting a new problem report in the forum, please take time to read what information is required to be provided in a problem report so as to enable both other users and the devs to better assist you!

If you have sufficient forum privileges please reply in a format conformant with the catalogue to this and the posts will be merged into the main post (please don’t edit this post to avoid conflicting edits)

The PR are grouped individual providers, and are numbered as follows S-YYYYMMDD-N
Where
S is the severity of the problem:

Critical meaning a total failure of a module to work at all (e.g. API change)
High meaning module is partially operational but requires work-around and so on.
Moderate meaning the module remains operational but causes inconvenience maybe requiring a work-around.
Trivial meaning the operation of the module is not affected (things like typos or UI colour scheme issues).

YYYYMMDD is the date the initial post with the problem report is made, and N is the sequence number for that day (in the unlikely event of more than ten reports for a single day, it’s a base-36 number 0-9A-Z).

A star (*) at the start indicates a change in the catalogue since the last update

jpp72

Sigh…

You guys are wasting your energy. I actually implemented a REAL bug and feature tracker and it was largely ignored by the powers that be, so i ended up shuttering it. Here’s a screenshot of what it looked like:

This was done before your time so that’s probably why you are optimistic about this…

0xFeedBeef

jpp72 users come here for reports, having a catalogue of open issues that’s on the forum enables users to see if someone has already encountered a problem that they’re experiencing and cross link straight to the thread with the problem report. The main goal was to reduce the number of separate posts with the same problem (yes, I know, it requires people to actually look through stickies in the first place)…

And while we (the end users) can’t force the devs to take note of the problem reports, it does work as indirect pressure as many potential customers check company’s support forums to see if the company’s worth dealing with… and the larger the number of open problem reports, the less inclined one is to part with their money…

Besides, the end users and undoubtedly the devs want the product to be better, and this is just a quick summary of single actionable things right on the forum (I think having the database hosted separately might’ve been a factor)