Dashboard problem with Release R65.15

nosnum

So, there was a problem with this release as described in the attached thread and it was admitted being a regression by Quicken updates - ok not a problem, software has bugs. Given this is a regression to existing functionality, I expected the problem to be fixed quickly - just revert the change that caused the issue and release whatever broke it later with a fix. Fast forward 4 months and the problem is still there, hey Quicken what's up?

I am an engineering manager for a cloud based software company. I actually own the infra used for deploying software across the fleet and our primary tenant is 'don't break existing use cases'. If you do, mitigate quickly with a fix, a revert or flip a flag to turn off whatever behavior was involved in the change. This keeps software flowing without having to roll back versions so that critical fixes can keep going out. After looking at the release notes for versions since this bug was introduced, you WANT the new versions given some of the descriptions but to accept that means I have to accept this bug not yet fix and the main dashboard I use to track my monthly expenses is busted in the process.

Quicken support, what is up here!?

Dashboard problem with Release R65.15 — Quicken

Quicken Laura

Hi @nosnum,

I sincerely apologize for how long this issue has persisted and for the frustration it has caused. I understand how important the budget progress bars in your custom Dashboard views are, and losing that visual feedback can impact how you track and manage your finances.

The case is still open, and there’s no official fix yet. I tested this on the latest version (R66.28), and the progress bars appear to be working. I recommend the following steps:

1. Back up your Quicken file
2. Update to R66.28
3. Check your custom Dashboard to see if the bars appear correctly

If the issue persists, please let me know. Thanks for your patience!

(CTP-15435)

nosnum

Hi Laura, no, the issue is not fixed in R66.28. If the patch that broke this is known what is the hold up? A review of the code that went into that patch and if needed a bisect if there can identify the offending code. Heck, you can even ask AI to do it and it will find the offending problem for you.

This seems like a very simple UI problem. The budget and actual values are correct and displayed on the screen but just no bars. Why is this so hard?

Quicken Anja

Hello @nosnum,

Thank you for following up—we completely understand your frustration.

While the issue may appear isolated to the UI, it has been more complex to resolve on the backend than it seems, which is why it has taken longer than expected. That said, the ticket (CTP-15435) is still actively being worked on, and a fix is currently in progress for a future release.

At this time, we do not have an ETA to share, but this has not been deprioritized. As soon as the fix is available, it will be included in a future update.

We appreciate your patience while this is being addressed! Thank you.

nosnum

Is there a way for me to track 'CTP-15435' to know when it will show up? I am not sure if release notes will call this out to know when resolved.

Quicken Laura

Hi @nosnum,

You can continue to use this thread to request updates. We’re able to check the CTP ticket for you and share any new information as it becomes available.

Thank you for your understanding.