Skip to content

[feature]: Status Tracking for Published Projects #8504

@Rodaviva29

Description

@Rodaviva29

Is there an existing issue for this?

  • I have searched the existing issues

Problem Statement

When someone reports a bug or request, if there is a published project, there's no easy way for them to track its progress without manual interaction or get updates individually. 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.

Proposed Solution

  • Enable subscription notifications for the whole project or a subscribe to a single work item (e.g. by email or another notification method) to keep the reporter updated.

Other suggestions:

  • Generate a tracking link for single reported work items that users can follow (public or private, just for them).
  • Allow internal teams to assign the details of reporters without the user needing to configure anything to get subscribed.

Relevant Context

This would function like an order status page but for issue tracking, like a Domino's Pizza order status, 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, https://i.imgur.com/TfC5W7l.png, https://i.imgur.com/e6MNQxG.png, https://i.imgur.com/KbmEEN0.png, https://i.imgur.com/q6kTqle.png.

Why should this be worked on?

It empowers communication with the community with minimal configuration and avoids the need for external tools. It makes 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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions