feat: Reporter Tracking for Public or Internal Issue Status
Problem Statement
When someone reports a bug or request, there's no easy way for them to track its progress or get updates individually, if I only want to be visible to the ones that reported the bug, for example. It becomes manual work to inform them about changes or to even remember the X member that did it in the past.
When users report a bug or suggestion, the experience often feels like throwing feedback into a black hole — they’re typically met with a generic message like “Thanks, we’ll forward this to the team,” with no way to follow up or know what happened next.
Recently, I encountered a much better experience when reporting a bug in the Revolut app. After submitting the report, I was able to track its progress directly within the app and even received notifications about updates. It made the process transparent and engaging. This kind of visibility builds trust and encourages users to contribute more feedback, knowing they won’t be left in the dark.
Proposed Solution
-
Generate a tracking link for reported issues that users can follow (public or private, just for them).
-
Enable subscribe notifications (e.g. by email or discord) to keep the reporter updated.
-
Allow internal teams to assign the details of reporter without the user needing to configure anything to get subscribed.
-
The URL should take to a simple screen with Status of the Issue and a couple of public details for them to see.
Relevant Context
This would function like an order status page but for issue tracking, like a Domino's Pizza Status Order, for example. Very useful for feedback workflows, especially with external testers, clients, or beta users.
Some examples: https://i.imgur.com/ER7kIni.png, https://i.imgur.com/EY7d6pM.png, https://i.imgur.com/BnZxhhA.png.
Does this feature align with Kaneo's focus on simplicity?
Yes, because it empowers communication with the community with minimal configuration and avoids the need for external tools.
🎯 Task created - feat: Reporter Tracking for Public or Internal Issue Status
Task Details
- Task ID: ytg1baz4m6rhesmaqwyk3wyf
- Priority: medium
- Status: to-do
This issue is automatically synchronized with your Kaneo project.
Some updates! I finally got some examples and my inspiration to suggest this in the first place!