Dashboard problem with Release R65.15
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!?
Comments
-
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:
- Back up your Quicken file
- Update to R66.28
- 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)
Quicken Laura
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
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?
0 -
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.
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
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.
0 -
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.
Quicken Laura
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
I just got an update to R67.7 and still no fix. The budget numbers are calculated correctly (allocated budget vs. actual usage) and show up on the screen. The only thing that is missing is the 'thermometer' that shows green/red and how far into the budget you have spent. This is how it has been since this got broken back in September (so the bug is now 7+ months old). There is no way this problem is so complex that it takes this long to fix. I suspect this got broken with the 'improvement' at the bottom of this note that feels related but again, new features should not be delivered that break existing behavior. This is so much core and simple functionality that I don't get why the delay. Here are the steps to reproduce
- Add a new view to the home screen
- Choose 'Budget' as a widget
- Add whatever items that you want to see and have budgets for
That's it the newly created view shows each item you choose from (3) but no graph, just budget on the left side next to the category, actual on the right side
- IMPROVED Added customization options to the Income Year-to-date snapshot on the Home Dashboard, including filters for account, category, and tag types.
This is beyond an acceptable time to fix an issue IMO and this really degrades confidence. Is this the best you can do here?
0 -
Hi @nosnum,
I understand how frustrating this has been, especially given how long the issue has persisted and how it impacts a core feature like the Budget widget. I also appreciate you taking the time to outline the steps to reproduce it so clearly.
At this time, there isn’t a new update to share on this issue. Our teams are aware of the problem and are continuing to work on implementing a fix, but we don’t yet have an estimated timeline.
We understand the impact of the missing “thermometer” visualization and apologize for the inconvenience.
Please know that as soon as we receive any updates or progress to share, we’ll be sure to communicate that here.
Quicken Laura
Make sure to sign up for the email digest to see a round up of your top posts.
0 -
Why do the developers continue to add new things that are of limited use and ignore fixing basic features of the program that are used extensively. Who prioritizes what gets done in what order? I really miss this feature and yet they continue to add stuff that just causes more problems with the basic functioning of the program.
1 -
+1. Quicken Laura, your post is exactly the same as the prior one. Quite honestly it looks like an AI response. I wonder if anyone is actually listening and responding. An AI agent can find and fix this bug in minutes. I say this because I have personally seen this in action and used such an agent to correct issues in software. It can even write tests to ensure such functionality doesn't get regressed in the future.
Along the lines of what @RichardSchreyer posted above, I say it again and even louder - Focus on ensuring reliability and stability first. Don't break existing functionality at the cost of new features. Bugs happen, I get it but prioritize fixing them over new things otherwise the can gets kicked down the road and you end up large tech debt and with situations like this. Laura, if you understood how frustrating this is you would not simply give us a rubber stamp answer and actually escalate this to the engineering team and get it fixed. You're the messenger, I understand, please deliver the message and get the team who broke this and can fix it to look at this thread and take action. Too often engineers are behind the wall and don't understand the implication of what they break - it would be good for them to see such frustration.
After nearly 4 decades in software engineering this is not just some rant, I am basing my response on reasonable and accepted engineering practices with acceptable and not over the top customer obsession. In my experience and job, mitigating regressions is measured in hours or maybe days depending on severity, not months. One last thing, sure, there is triage and priority - yes, fix the most important bugs first but are you telling me you have so many critical bugs (like correctness and corruption) that this is not bubbling up in priority after 7+ months?
1 -
Hello @nosnum & @RichardSchreyer,
We understand the frustration here.
On the technical side, I don’t have additional internal detail beyond what’s already been shared in the thread (CTP-15435 is still open and actively being worked). We understand that’s not the level of specificity you’re asking for, but that’s currently the extent of what’s available for public updates.
As for Quicken Laura—she is not an AI system. Like my self, she’s a real person and a member of our Community moderation team. We relay the information available to us from internal ticket updates. I understand how responses can feel templated when updates are limited, but there is a real team behind these replies working to coordinate between users, support, and escalation channels.
In terms of prioritization and timelines, issues like this are tracked and escalated internally, but we don’t have visibility into engineering sequencing or release scheduling from the Community side. I know that’s not ideal, but that’s the current structure of how updates are communicated.
Thank you both for continuing to document the behavior and share detailed feedback.
We appreciate your patience while this is being worked on!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
Thanks, An AI is also smart enough to say it is not AI lol (I'll take your word for it tho!) You've unfortunately not addressed any of my comments other than to say you've forwarded it on to quicken. I thought you actually worked for Quicken and had the insight and to what was going on (my apologies) but it seems you are as in the dark as we are. I am not sure the value of this moderation is then. I hope from my responses you can see I am not some whiny disgruntled user. It would be nice if someone from Quicken can actually address my reasonable and hopefully well-articulated points.
0
