Can someone (at Quicken) explain why the below thread was 'closed' without any reason, fix or updates?
Hi @auga,
Thank you for reaching out.
Community threads are typically closed after a period of inactivity, usually around one month. However, a closed thread does not indicate that work on the issue has stopped. The case remains open and is currently awaiting implementation.
At this time, we do not have an estimated timeframe for the completion of the implementation. Any new information or progress updates will be shared through the Community Alert as soon as they become available.
I understand this may not be the update you were hoping for, and I recognize that a more specific timeline would be helpful. Unfortunately, the information above is all that is currently available for us to share.
Thank you for your patience and understanding. We appreciate your continued interest in this issue and will provide updates as soon as we have more information.
(Ticket #11616921 / CTP-12275)
If you want to make sure a thread is kept open, be sure to post something in it at least every 2-3 weeks….even if it is to say that you are still encountering the issue or to ask for a status update. That will show there is still activity and interest in keeping it open and that the topic has not gone stale.
@Boatnmaniac [Removed-Inappropriate] Thanks for your suggestion, but I don't appreciate the extra effort that Quicken expects of it's users to keep a conversation open regarding a bug that they acknowledged more than 18 months ago.
My perspective on this: How is Quicken supposed to know if an issue raised in a thread is still an issue for users if those users don't periodically tell them that it is? There are a tremendous number of threads where users simply stop posting in the thread. And even when prompted it is common that no responses are posted. Those posts generally need to be closed out or this forum become overly cluttered and unwieldly and, therefore, much less useful.
This past winter the Moderators have started to post in threads asking whether the user(s) still need assistance. Generally they now give at least 2 such prompt posts. No response from the users in the thread will result in the thread being closed. IMHO that is a pretty good process that takes the onus off of users to try to proactively remember to post something in a thread to keep it open.
I had suggested posting something in a thread every 3 wks or so to ensure the thread stays open. But your other option is to wait for a Moderator to post a prompt and then respond at that point. Either way, a new post being made will help to ensure that the thread will remain open for about another month. Rinse and repeat for as long as the issue remains open.
I am also getting "everything else" budget numbers that are insane and I can't get rid of them. The false numbers are attached to one category and go away if I just omit that category - bad way to run a budget report. The "everything else" numbers don't seem to be included in the totals and subtotals so you can just cross the line out in your report and ignore them. This has been a problem for at least the last year. Will this bug ever get fixed?
