So I think you may be misunderstanding or not actually testing this yourself...Just to give you some more proof of this bug.
1. I disabled ALL of my rules (94) of them except for one. I then edited the rule to include only a SINGLE condition. So at this point we can agree that there can be no possibility of confusion between or within any rules right?
2. I did an undo on one of the transactions that matched the rule still active.
3. I then ran "update" which should have recognized the transaction and auto-confirmed. It did not.
4. I then went to the active rule, clicked edit, and save, did not change any details, and poof, the transaction has been confirmed.
5. Its clear that "updating accounts" and "editing a rule" are different processes but, its also clear that the end result should be the same, a confirmed transaction...
6. Now you may claim that since I undid this transaction, the system marks it somehow and doesnt allow it to be auto-confirmed, I would ask you to prove that with the engineers. I would then ask well...why then does editing a rule auto-confirm it...?
7. While I do have 94 rules, i do not have any obvious "duplicates." If your claim is that there are duplicates, the system should have logs that can show us exactly what is causing the problem so that we can actually FIX THE ISSUE, what a novel idea...
8. Your answer is super vague at best "some users have reported if two rules are set to look for "withdrawal" transactions, one (or both) of them won't work." Even you are admitting that this is a bug! This should work, it should process based on priority.
9. And lastly, I cannot confirm 100%, but to me it looks like the rules are categorizing EVERYTHING properly, however, they are just not auto-confirming. I changed the category for a transaction and ran "Update" and it changed the category back based on the rule, but didnt auto-confirm. This is why I came to this conclusion.
10. Quickbooks support should actually push these claims to engineering to FIX an obvious bug instead of providing work arounds to all their paying customers.
11. This was all tested in multiple supported browses cleared cache etc, nothing fixed the problem.
