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

Reporting bugs from Quicken for Windows

Stripedbass411

What is the best way to report a problem when a bug is found in Quicken for Windows? In the past I have tried both calling the Technical support line and by submitting a report via the Quicken help "Report a problem..." feature. Whatever way I try to bring some light to the problem the bugs remain unaddressed and they seem to remain ignored. There is no way that I can find for getting the status of when the bugs will be fixed or where the bugs reside in the development team's queue to address.

This becomes quite frustrating because the problems are related to basic functionality that should be working or had worked in the past and is now broken from a newer Quicken release.

Ideally, there is a way to report bugs through the Quicken Community site so that once reported the development team will be alerted so the problem can be properly address along with a ticket number being attached to the report so myself any other in the community are able to track its progress. This would also allow for others to see that the bug has been reported which would cut down on possible reoccurring reports to the development team on the same bug.

Find more posts tagged with

Accepted answers

NotACPA

Why don't you try reporting your alledged bugs here? 1 per thread, please.

Stripedbass411

@MontanaKarl Thank you very much.

I've been using Quicken for thirty-three years now and being a developer myself it has been frustrating not being able to convey bugs back to the development team and seeing them get fixed at some point in time. When the "Report a problem" was introduced in Quicken I thought that was a great way to channel issues but like you said it seems as though the reporting goes into a black hole and calling the Quicken Technical Support line for status never results in anything either.

I'll take your advice and try to report a few bugs in the "Quicken for Windows" / "Errors and Troubleshooting" sub forum.

Greg_the_Geek

FWIW, you can join the beta test team and report bugs which should go to development.

All comments

NotACPA

Why don't you try reporting your alledged bugs here? 1 per thread, please.

q_lurker

While you can certainly bring your identified “bug” to the attention of this community for confirmation, validation, and discussion, that does not automatically get it to the attention of the development staff. Fellow users in the community may be able to offer workarounds and broad support may increase the chance of development taking notice, but no guarantees.

Stripedbass411

@NotACPA -

When you mentioned to try reporting the bug here are you referring to creating a new inquiry in the community as a "New Discussion" post or as an "Ask a Question" post?

Unless my understanding of the community is wrong I thought a "New Discussion" post is simply that, a post which other community members can comment on where those other members really have no channel to redirect issues to Quicken development. On the other hand, I was under the impression that the "Ask a Question" posts only get picked up by the moderators of the community and moderators just keep order in the community without a channel to redirect issues to Quicken development.

Please clarify - thanks.

MontanaKarl

@Stripedbass411 Overall, yes, the Community is for user to user discussions. Each product line has an “Errors and Troubleshooting” subforum - such as the one we're in right now for Windows - where bugs can be reported for other users to verify. While “Report a Problem” frustrates all of us - as there is never even an acknowledgement that the report has been sent, much less a case number - opening a thread here with details, including screenshots, allows you to include a link to this thread in your “Report a Problem report”… making it easy for others who can reproduce the same problem to simply include the thread link in their report.

Stripedbass411

Greg_the_Geek

FWIW, you can join the beta test team and report bugs which should go to development.

Stripedbass411

@Greg_the_Geek - Thank you for the input. The beta program was considered in the early days of Quicken and as time past I decided against it because the thought of using beta software with my finances did not sit well with me.

Greg_the_Geek

You can always do as many testers do and create a VM to run the beta version of Quicken.