Hi,
It would help a lot if you would mention (major) bug fixes in the release notes. It would help a lot not only for troubleshooting (faster time to response, less request to your support team) for on-premise installations, but to also know at which level we need to update the system to fix the issues. As of now, we only see new functionalities mainly.
Cheers,
Damien
Do you like this idea?
Dear Damien,
Thanks for sharing your idea!
If you need assistance with a specific bug, please provide us its example and we'll quickly fix it! in general, we fix the errors immediately and provide a fix for the version the issue occurred or in the next releases.
In release notes, we mostly focus on new features that were introduced in a release.
Please let us know if additional questions arise, we would gladly assist you!
Best regards,
Anastasiia
This is a very long awaited idea, that will make life much easier for all of us
Hi Anastasiia Marushenko,
Happy to know you will provide assistance ?
However, let me provide you a counter example (I have others, but this is a simple one) about the quick fixes:
In 8.0.2 there's a rather large display bug wanting to the see detail behind a graph created in a dashboard done in with the latest Freedom Designer UI, that , after asking support for assistance, will "only" be fixed in 8.0.3. This is great news: there's a bug in a minor release, and you fix it straight in the next one. However, I probably am not the only one that reported it, but should I had read it in the release notes, I would not have needed to take time to report it and your team take time to answer back that it will be fixed in 8.0.3. I save time, you save time.
2nd scenario - 8.0.3 brings a new feature to handle shared emails in Oauth as Microsoft will deprecate starting Oct 1st. It's a very important feature for one client, and we have to upgrade. But for others, it is not. One client will be upgraded, the others will wait.
But, what is true for new features, is also true for bugs. Maybe there's an issue at one release (major or minor) that can be a real problem for a particular client. Then it can also be a choice not to upgrade to that version and we wait for the next. Upgrade on on-premise instances is costly, and we need to make sure we
It's normal in an application's life that bugs arise that needs fixing, and we are fine with that ?. What we are not fine with is the lack of information.
"In release notes, we mostly focus on new features that were introduced in a release." --> that is exactly the issue we have - release notes are incomplete, focusing on new features only.
If you look at top notch applications, you will notice there release notes includes: new features, bug fixed and sometimes known issues.
Hopes this clarifies the needs.
Cheers!
Damien
p.s. Not sure what's going on with the italics above, cannot remove it ;)