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; } } }

Dashboard problem with Release R65.15

nosnum

I see the prior post was closed but the issue is not fixed. Can we not leave this open to show it is a current problem that is not yet solved? I cannot reopen myself nor can i add comments so I am opening a new post. I just updated to R69.21 and the issue still exists.

Dashboard problem with Release R65.15 - Quicken

@Quicken Anja you mention the problem is reported and is being worked on in a future release. The problem is coming up on a year since it was introduced. I experience this problem every day since I use quicken every day and each day it surfaces on startup and I have to work around the issue.

Find more posts tagged with

Windows

Dashboard

Comments

RichardSchreyer

This and scrolling have motivated me to move on to a different product….Consider Quicken to be one of my legacy systems that will be used for historical reporting purposes only. One less subscription to worry about.

Quicken Kristina

Hello @nosnum,

Thank you for reaching out! Discussions on the Community are not the same as contacting Quicken Support directly via phone or chat. Discussions aren't support tickets, and they're closed after about a month of inactivity, even if the issue isn't resolved.

While the discussion is closed, the ticket created to report the issue is still open. There are no new updates, but I can see that our team is working on the issue.

Thank you!

(CTP-15435)

nosnum

Hi @Quicken Kristina , thanks for the info. I get what you are saying. I do find it a bit challenging tho if you don't give us access to the status of CTP-15435, I have to keep guessing if it is closed / fixed and each update I need to 'check'. The release notes don't specify the ticket numbers which make them useless from our perspective.

I am going to be a bit harsh here when you say you can see the team is working on the issue, I find that difficult to believe since the problem is almost a year old (unless they just picked it up). I'll close by stating again I am a recently retired software engineer and engineering manager for a cloud based SAS company. In fact, I owned the engineering for release management and understand the mechanics of delivering software at scale in the cloud. This is a regression created by an update that was allowed to remain for a year - this is completely unacceptable, especially with the current AI capabilities. By the way I understand your position, you and @Quicken Anja are just in the middle and have to give the party line answers here. It is too bad Quicken is not more customer obsessed.

If you want to close this thread based on your comment feel free. I won't be updating on this thread again based on the feedback from you both.

Quicken Kristina

Thank you for sharing your feedback!

I forwarded it internally.

Thank you!