EuroDK delivers CRS226 devices with not so recent firmware: 
It reveals a WinBox 3.7 bug:
In WinBox 3.7, when clicking “Quick Set”, WinBox hangs and never shows the dialog.
–jeroen
Update and don’t use quickset. Make the settings directly without the quickset.
I guess he is just reporting the bug.. More luck reporting at support [at] mikrotik.com
Sent from my SM-N910C using Tapatalk
Indeed.
I stopped reporting bugs using private means whenever no private details are involved. Makes is much easier to track and for others to follow/comment on.
So above is the bug report; please administer in your systems the way you can handle it best.
The problem with this approach is this is a user forum, and not an official support platform. And unless you write to support@ your report is very likely to remain completely unnoticed by the Mikrotik staff.
so the best way is to do both!
Sent from my SM-N910C using Tapatalk
I got at the forum through http://www.mikrotik.com/support which nowhere mentions the forum is anything else than an official support platform, so unless Mikrotik changes that page, I will assume they actively monitor this forum for support issues.
–jeroen
They don’t. But you can assume whatever you’re comfortable with.
By the way, the page you’re referring to clearly says:
- Don’t forget to check our community forum.
The key work here is “community”.
I stopped reporting bugs using private means whenever no private details are involved. Makes is much easier to track and for others to follow/comment on.
That is not a good idea. It is very difficult to track each response in the forum. If you want MikroTik staff to accept your report, please email it to support@mikrotik.com
Also see Forum FAQ: http://forum.mikrotik.com/faq.php
I think it’s a splendid idea: I’m all for publicly visible bug tracking.
Tracking with RSS is easy to setup: https://www.phpbb.com/community/viewtopic.php?f=46&t=2098171
Or even better: do your bug tracking in something like GitHub so it becomes very simple for the general public to track things and see if issues have been reported before. You don’t even need to have your repository on GitHub for that. Similarly you could use JIRA for this.
The cloud has evolved; e-mail is for private stuff and rapidly diminishing. Same for public stuff and newsgroups or even forums. QA is rapidly moving to platforms like StackExchange because it is way easier to have the good content stand out above the not so good content. Similarly documentation projects love the WiKi format.
–jeroen
This has been discussed before.
Not all bugs are affecting everyone, not all bugs should be made public, not all complaints in the forum are bugs.
In that case I will use e-mail and schedule parts of the resulting thread as blog posts so they are part of my publicly searchable knowledge base at my discretion.
–jeroen