Feature request for product/service
Describe the request
I’d like to propose a feature for the forum that would allow users to “track” specific bug reports and feature requests.
The Problem: A Disconnected Community Feedback Loop
Currently, the process for reporting and resolving issues can feel a bit like a black box for the end-user. The feedback loop from the forum could be more transparent and measurable for the benefit of of both customers and Cursor.
Here’s a common scenario:
One or more users report a recurring issue (e.g., problems with the integrated terminal).
The team acknowledges it with a helpful, but general, reply like, “Thanks for the report, we are working on it.”
Time passes, and new versions of Cursor are released with their changelogs.
The original reporters have to manually scan each changelog to see if their specific issue has been addressed. The connection between the initial report and the final fix is often lost.
The Proposal: A New, Connected Feedback Loop
I propose implementing a system that directly connects users to the issues they care about. This could take a few forms, but the core idea is to create an explicit link between a user’s report and the eventual solution.
Key Features:
“Track Issue” or “Subscribe” Button: On each thread, allow users to click a button to subscribe to updates for that specific issue.
Automated Notifications: When a fix related to a tracked issue is shipped in a new release, automatically notify everyone who subscribed. This could be an email or a forum notification.
Linkage to Changelogs: The notification should ideally link back to the original forum post and the specific line in the changelog that addresses the fix. (Not sure if this is viable/suitable, but one benefit could be to reenforce the value of community contributions.
How It Would Work in Practice:
A user reports the “Terminal Problem.” Other users experiencing it comment and also click “Track Issue.”
A tag on the post or a landing page somewhere else which might change from Reported → Investigating → Fixed.
When Cursor releases v0.26.0, the changelog notes the terminal fix.
An automated reply is posted in the original thread: “This issue has been addressed in version 0.26.0. Thank you for your report!”
All users who tracked the issue receive a notification with this update.
The Benefits:
This system would create a powerful, positive feedback cycle with several advantages:
Improved Customer Satisfaction: Users would feel heard and valued, knowing their specific contributions are acknowledged. It closes the loop and shows that their time spent reporting the issue was worthwhile.
Targeted Quality Assurance: The notification could include a simple, direct follow-up poll:
“Did version 0.26.0 fix the terminal issue for you? [Yes] / [No]”
Better Data: If a user clicks [No], they could be prompted for more detail (“Please explain if the issue persists or has changed.”), providing the development team with immediate, high-quality data on whether a fix was truly effective.
Increased Transparency: It would give the community a much clearer, real-time view of what is being worked on and what has been resolved.
Thank you for considering this request. I believe a feature like this would significantly enhance the relationship between your team and the community, and ultimately help build an even better product.