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

What's the process for getting an acknowledgement of a bug report, and that it is being addressed?

jmaino

Hi - back in Jan, I reported this newly arrived bug as of r46-9:
https://community.quicken.com/discussion/7928499/r46-9-bug-error-when-entering-new-securities-manually-edit#latest

Had a nice convo w/ q_lurker at that time, who could reproduce the finding and had a thought as to the root cause.

However, the problem persists - I've reported it thru Quicken itself as well.

Is there a process by which I can know if/that this is ack'ed by Quicken, and is planned to be addressed?

thanks

Find more posts tagged with

Comments

unknown

This content has been removed.

NotACPA

There is NO acknowledgement, other than replies from other users, and NO feedback from Q until/if it's fixed. Things just don't work that way.