I really like the idea of making it easier for those with issues to understand if we’re already aware of issues, or if a fix is on its way.
However, as much as we try and squash all the bugs we find, as the apps get more complex, and the company and customer-base grows, the number of issues will do so too - there are times where a bug can’t be fixed for a while due to other issues being more important, or because we don’t have enough information to diagnose the bug and fix it.
Especially due to the nature of bugs, it’s also tough to know which issues are duplicates or related at a glance, which might make it tricky for a customer to even work out if what they experienced is already on the ‘bugboard’ or not.
Keeping an up to date, publicly understandable version of current bugs would likely become a bit of an admin nightmare, and cost more to manage than it would be to talk to our support team and get a more informed answer.
However, one thing we are trying - which we might be able to learn something from in order to help with this problem, is making it easier to find out what we’re working on regarding features, from within the Monzo app itself. For instance, if you find a bug related to the Spending tab, but can see we’re in the process of completely re-writing it, maybe it’ll help to know things will be changing soon anyway. You should see our first tests around this in your app soon.
Hope this helps, and doesn’t read as too much of a dampener!