Maddy on 14 Aug, 2020 01:45 PM
Thanks for the suggestion for improving Moneydance! I've filed a ticket in our ticketing system with your suggestion, explaining the specific details you have requested, so the developers will be looking into it.
Please let us know if we can be of further assistance!
I do not believe I have seen an explanation of how suggestions work, but having worked in the industry I can outline the general approach used.
When someone makes a request an acknowledgement is usually provided, as has happened here
Suggestions or requests for features are generally recorded in some sort of system, usually a data base type of system, where the details are entered as well as follow up information. Also details of further interest in such a feature is also added to the data.
This sort of data is viewed by Product Management when they are planning future releases. Many factors can come into what features or suggestions are to be implemented. amount of worked required, product direction, interest in the feature etc, usually the requests will get priority levels assigned. Where I worked a P0 meant the product could not ship without that feature, P1 meant it could ship but the feature should be provided at the first update and it goes on from there. The company had a very detailed procedure to decide what features are to be included and to get approvals etc.
It is unusal to be advised that the feature is going to be implemented, but one thing I feel that TIK should do is advise if a feature request has been rejected and close it off. This may seem harsh but some requests will never be implemented, a simple example is that I have seen people want to be able to keep one side of a transaction when they delete the other side because they want to completely delete an obsolete account, as Moneydance is built using Double entry accounting principles this is an invalid thing to do, the whole architecture of the program would need to change to be a single entry system and that breaks how the software works.
Outside of the company you never see what has been suggested, what priorities are assigned or a timeline, timelines are only ever assigned when it is decided to include a feature, but that becomes the timeline of that version which again Moneydance does not publish. Where I was once a new version was planned we did provide customers with some updates on the future version but that was usually done under legally binding non-disclosure agreements, not via public news releases.
With Moneydance you may see some features just happen almost instantly. This is generally because in the code the change required to do it is fairly minor and it becomes just a maintenance task. Something that may seem major to you could in fact be minor, yet something that looks pretty trivial could require considerable programming to achieve, looks can be deceptive.
What I have outlined is a very formal process, as a very small company I would expect TIK to not be quite that formal but the general principles remain.
Thanks for the detail. My complaint is I never get any acknowledgment unless I post something in extension development. I guess the developer monitors that as he responds pretty quickly. Posting in the suggestions or problem areas I seldom get even an acknowledgment. In this case, a user brings up an old request and gets an immediate response. And an issue is opened. This is a major enhancement (IMHO).
I'd just like IK to give a broad description of the process. Perhaps as you suggest, my 'problem' is insignificant.
Thanks for your input.
Yes support should communicate more and also better, that would solve a lot of frustration at the very least.
I do not believe your request is on the insignificant end of the scale, A lot of the data is potentially present, in that the Cheque number is there, also potential the account number and bank numbers are also present. Even if you discount the ink issue, which is still a requirement in many parts of the world there are standard for the layout of the line that can vary. This can relate to position, size and certainly to layout and punctuation.
As you said in your case your bank uses OCR, but what about all the clearing systems and other banks that the cheque may have to go through if it is lodged with a party other than your bank. I would expect there to be a national standard that has to be adhered to.