Budgeting Does not work in Quicken for Mac

@gr802 I know you're frustrated, but let me try to provide some information about this forum and Quicken…

First, posts in this forum are closed after a month of no new posts. It has nothing to do with whether an issue was resolved or not. This can seem like a bad rule, but it avoids having users add to an older post with a "me too" reply to an issue which may have been addressed or changed, or may not even be the same issue. So while it may seem arbitrary, that's the way they choose to run this forum.

This forum is not Quicken Support. The Quicken moderators try to help answer certain questions, but they are not Quicken Support.

Quicken developers may or may not see every post on this forum, but they don't reply on this site or engage in dialog with users here. Similarly, if you submit a problem report, they never respond to those (unless they need additional information). That doesn't mean they haven't seen a problem report; there's just no way to know if they've replicated the issue or if/when they plan to address it.

If you want a dialog/confirmation about the issue, your best bet is to call Quicken Support (during the week; they're close on weekends), and have a representative do a screen share with you so they can see what you're seeing; hopefully, they'd then document it for escalation and provide you with a ticket number which can can later follow up on. I think you said in your prior thread that you had called Support. Did you get a ticket number? If you post the ticket number here, a moderator can check to see if there is any update on that status. (But often there's no update until the issue has been resolved.)

Finally, even if the developers receive your report and verify that there is a bug, that doesn't mean it will be promptly addressed. Quicken, like almost every software developer, has many bugs which have not been addressed for any number of reasons: deemed too minor, deemed affecting too few people to spend time on, involves an area of the program which is slated for future revision/rewriting, etc. A given bug could require a change in one line of code, or a major rewrite of a significant piece of code. A bug might be addressed in the next release, or slated for a fix in a future development cycle, or pushed off indefinitely.

In this case, we know that Quicken has long planned to revamp or rewrite parts of the budget code in Quicken Mac in order to add functionality users have asked for. So it may be that even if you've encountered a bona fide bug, they might choose not to address it in the short-term because that section of code is being (or scheduled to be) rewritten. Or… they might be planning on a fix for the next release.