nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Criticality-Driven Priority of Bug Fixes

MSStateDawg

I see hordes of users complaining about the downloaded trans matching bug (Quicken creates a new trans rather than using the existing trans with which it matches), but we continue to see bug fixes for issues about which I see minimal complaints.

Am I just missing the feedback about the issues that are being fixed or does the Product Manager have an issue with prioritization?

Find more posts tagged with

Accepted answers

Sceptic

@MSStateDawg I understand your frustration. One thing to keep in mind is that forum posts only provide a partial view of what the development team is evaluating. While a particular issue may generate a large number of public complaints, Quicken also has access to data that users don't see, such as support case volumes, crash reports, internal telemetry, severity assessments, and the complexity of potential fixes.

It's certainly fair to question whether a specific issue is receiving enough attention, especially if it affects your daily workflow. However, the fact that other fixes are appearing in release notes doesn't necessarily mean this issue is being ignored or considered less important. Some bugs may be relatively quick to resolve, while others can require significant changes to core functionality and take much longer to investigate and correct.

As fellow users, we generally don't have visibility into the Product Manager's prioritization process, so it's difficult to know exactly where a particular bug stands in the development queue. Continued reporting, providing reproducible examples, and adding your experience to existing discussions are often the best ways to help demonstrate the impact of the issue.

All comments

Sceptic

Jim_Harman

You aren't missing the long resolution times for several recent Quicken bugs that appear to affect a lot of users. These are particularly troublesome because they appear to have been caused by side effects of recently introduced changes or features.

Here is a summary of the pressing issues I see, along with their tracking numbers and some stats from the Community.

Description	Date reported	Views	Comments
Downloaded transaction mismatch/duplication when matching to Reminders (CTP-16297)	4/2/26	7,400	197
Scrolling issues with mouse wheel and downloaded transactions pending CTP-17721/QWIN-27833)	7/1/26	6,400	177
Can't clear splits in transactions from a memorized payee using the red X when manually entering a transaction or accepting a downloaded one (CTP-18503)	9/9/26	715	33
Values changing when editing splits and navigating with Tab (CTP-18406/CTP18407)	9/18/26	421	19
Can't enter zero-value splits when navigating with Tab (CTP-18429)	9/3/26	590	20
Portfolio X-Ray - ETFs shown as Unclassified (CTP-18131)	8/6/26	510	21

I'm sure there are more, will add them as I find them

MSStateDawg

Seeing your response makes me feel so good that resources were used to address the following critical issues:

IMPROVED Added a report preference for short sale gain and loss reporting in the Schedule D report.

IMPROVED Improved the investment transaction search results dialog layout and column labels.

IMPROVED Improved the Add Security window and made the instructions to add crypto and precious metals easier to find.