Description

Hi,

I have a minor bug to report (minor, but it costs me time each time I use MD!): If I download transactions and MD incorrectly proposes a match, when I set the item as "no match," MD sets the category for the transaction back to the account's default category -- even if MD would have automatically and correctly set the category because of previous transactions with the same payee. In other words, if MD had not incorrectly tried to match the transaction (and had set it as new from the start), then MD would have set the category correctly. It would be great if this could be fixed, so that when you unmatch the transaction, MD then decides what category to use (usually it's really smart and gets it right) and doesn't just fall back to the account's default.

In case it matters, this is MD 609 on Ubuntu 8.04 with Sun Java 1.60_06.

Thanks, Marc