We would like to express our concern regarding the recurring issues that appear after recent software updates.
Kindly, we request that updates be thoroughly tested before release, as we are repeatedly facing critical problems after each update and are forced to wait for fixes and patches. This directly affects our daily operations and causes delays in issuing invoices, which creates serious problems with our customers and accounting workflow.
Recently, we have experienced multiple issues related to invoice issuance, quotations, credit notes/returns, and unexpected changes in theme layouts and formatting after updates. These problems significantly affect our work and require additional time to correct and recheck documents before sending them to customers.
I would also like to mention that I have been using the cloud version of Manager.io for more than five years and rely heavily on the system for our daily business operations and e-invoicing processes. Therefore, system stability is extremely important to us.
We appreciate your efforts in improving the software; however, reliability and stability are essential for businesses depending on Manager.io and ZATCA compliance.
We hope future updates will undergo more comprehensive testing before being released to users.
Agreed. This is something of a recurring theme and has been brought up before. It is impossible to know what the next thing to be broken will be. The updates just happen and regularliy to require a scramble/effort to get things working again.
Just in the last week, tags stopped working in email templates (except for {{reference}}), my book-keeper sent out dozens of invoices with emails full of ‘code’ as a reault that looked very unprofessional. The New Receipt button vanished from Sales Invoices and my front office person who enters receipts got totally lost (it’s all she knew) - I only found out a couple of days later we were way behind.
While from a development (as Lubos put it - inside perspective) these changes might feel minor, from a user and/or external third party communication perspective unexpected changes like this not only impact established processes but can make us look bad when things get sent to customers that are messed up.
There have been many threads on this over the last couple of years but it just keeps coming. Surely there must be a way to have a test (beta) environment, recruit some users as testers and have an advance plan with impact areas identified and cut-over/change tasks and then periodic ‘published releases’ to the production environment so that folks have adequate notice to address upcoming changes?
@lubos Thank you for your continued support and development of Manager. We all love it, but any thoughts on how we can all work together to better manage updates and the need for manager users to tackle fire-fights whenever updates impact fucntionality, UI or third party communications? Thank you in advance for discussing with the community.
@alasdair I stand corrected. Agile does not imply inadequately tested deployment. Also using Agile as a justification for releasing versions that users then have to debug is also wrong. There is some balance in that Agile encourages user feedback, but that does not mean outsourcing Quality Assurance to users.
I agreed to this also. I am running Manager server version. I am always waiting with updating my server version after consulting the forum for the problems that are found recently. I am never running the latest version.
