Auto-close timeframe for bugs is only 20 days! Far too short!

Feature request for product/service

Describe the request

It appears that bug reports get auto-closed after a MERE 20 days!! I have numerous bugs that were filed just over 20 days ago, and ALL of them have been closed, while none have been resolved.

A 20-day window is far, far too short a timeframe, when the Cursor team does not seem to be resolving LONG-STANDING issues even over a period of months. There are outstanding issues with @ commands as well as custom / commands, and numerous other issues, that have been extant for months, and have had no resolution and no report even on whether or when they will be resolved, and many had no response at all.

If bugs take months to resolve, then the bug reports will need to remain open for that long as well, so that continued discussion can occur on them. I have been re-encountering many bugs that have been problems since as far back as August, that are still not resolved, and for which no resolution appears to be in sight.

Please extend the auto-close timeframe for your bugs. Closing them so preemptively is creating an illusion of resolution, when no resolution actually exists, and a plethora of bugs not only still exist, but in some cases seem to have become worse over time.

Operating System (if it applies)

Windows 10/11
MacOS
Linux