For one, it’s an issue on the openhab-core repo, not the openhab-addons2 repo. It is important to see where an issue is to understand what it applies to. And if the issue is in the addons2 repo, it will usually start with the binding name in brackets (e.g. “[mqtt] Something doesn’t work with blah”).
It has been stated multiple times on the forum in many many threads. To get the attention of the developers/maintainers you must file an issue. If there is somewhere it would be appropriate to add that to the docs I’ll do it, even though I know no one will read it.
And I created How to file an Issue for people to link to when something that looks like a bug is discovered on the forum. For all the people helping on the forum and maintainers (I hope you all see this) please make a point of linking to that thread and asking users to file issues when a problem appears to be a bug.
The developers spend their time coding, not reading each and every posting. And not all of the developers participate on the forum. A forum thread has a very good chance of being missed. GitHub is where the full development workflow resides. The developers can ignore the issue, or decide not to code the fix or feature request, but they wont miss the report in the first place.
Because the issues on github are part of what drives the development, an issue must always be filed whether or not it’s also reported on the forum. As Kai said, if there is no issue, the bug doesn’t exist (or at least it doesn’t exist in the development workflow which is the only place where work occurs to actually fix the bug.
And who is the best person to file the issue? The person who is experiencing the problem in the first place. It does no good for me or someone else to create an issue for a problem that I’m not experiencing. I can’t answer questions from the developer. I can’t provide the steps necessary to reproduce the bug.
An open source project like openHAB is a community effort. It is not just the developers and maintainers who have a responsibility to the community. We all have a responsibility to the community. And part of that responsibility is filing issues on GitHub when you encounter a bug. If you are not willing to register on GitHub, I’m afraid that means you are not willing to live up to your responsibilities. As I discussed above, someone else can’t file the issue for you. So if you are not willing to do your part, it doesn’t seem fair to be upset when the developers don’t fix it.