I cannot seem to reprioritize transaction rules. Other users are also reporting this issue. There are at least two threads on the subject…neither of which has garnered much attention.
Please, could someone at QB verify that reprioritizing rules is a problem and provide a workaround? I don’t think the priority list can be edited any other way. I do not see a field to change the priority number manually. I do not see another UI widget to accomplish a reprioritization. If there is no workaround, could someone at QB please acknowledge the issue is being addressed?
Note that I have already cleared my cache, deleted cookies, gone incognito, logged in and out, used different browsers, posted replies to the other threads, and engaged in a screenshare session with online support. The issue persists unabated.
Just an obvious fyi: The inability to reprioritize rules is a bit of a problem. This is because new rules, upon creation, are added to the bottom of the rules list and are, therefore, treated as the lowest priority. As such, if newly-inserted, lowest-priority rules are more specific than rules above them in the rules list, those newly-inserted rules will never be applied. This is because more general, higher priority rules will intercept applicable transactions and apply their attributes—preventing the new, more specific, lower priority rules from applying their attributes.
In order to stop this interception, new rules (once added to the bottom of the list by the system) must be dragged-and-dropped to a priority location in the list above the more general rules (see attached image). This cannot be done. The functionality is broken. The drag-and-drop feature is missing. It is no longer available. The handles that used to appear in the left-most column are gone. Users cannot reprioritize transaction rules. Therefore, users cannot create new rules and expect them to be applied if any existing rule can already apply to the transaction. In essence, users might no longer be able to create new transaction rules and expect them to be applied.
Topically, in my case, a general default expense rule exists as the last rule in the list. The last rule in the list applies to any expense transaction (splitting the expense transaction percentage-wise amongst several partners and then categorizing it as a root expense...after which a bookkeeper recategorizes it more specifically). Because this general default expense rule exists and applies to any expense, no new specific expense rules will ever be executed because this general default rule will intercept and apply its attributes before reaching the new specific rules added to the bottom of the transaction rules list. Therefore, I can no longer create new expense-related transaction rules. Since the feature broke, I have accumulated a dozen or so new rules that I cannot implement. I am essentially prevented from creating any new rules until the problem is fixed.
If anyone can help, I would appreciate it. Thank you to anyone who may respond with pertinent, substantive information.
