Publishing changes to Onebox OS, Changelog

In my opinion, and I am 1000% convinced of this, that stopping the Changelog is the biggest mistake made by the OneBox administration in all the time that we have been using this CRM. You can't come up with a more terrible decision than stopping the Changelog. I will try to explain briefly. Everyone who is involved in setting up and improving the CRM understands perfectly well that any, even the most complex business process can be planned for months, everything can be thought out to the smallest detail, but at some point, the entire idea can be made unviable by the absence of some "check mark", or an option in action, some little thing prevents the implementation of everything planned. To get around this, the integrator and the customer begin to create some kind of crutches, improvements, intermediate stages and other heresy! And the problem is all in some check mark. As a result, some ideas and projects simply do not reach their logical conclusion due to the banal absence of some elementary functionality. Very often, someone does some improvements and long-awaited functions appear in the actions and functionality that make life better and the system more functional. But!!! Nobody the f**k knows about them!!! And no one even guesses that these functions have appeared! And this is a very common occurrence, when users do not even guess that yesterday or the day before yesterday some functionality appeared that they have been waiting for the last years. The absence of Changelog is a disgusting phenomenon, and I frankly do not understand why the developers and owners of such a cool CRM are frankly dumb in this place. Personally, I read these Changelogs and followed them every day. After it was removed, life was divided into "before" and "after". Stop! Bring back Changelog!

Also for bringing back the Changelog. It was very convenient to find out about updates.