Allow choosing which events (closure, etcetera) to subscribe to notifications of, per issue and MR.
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Users should be able to subscribe to solely issues and merge requests' “Close” and “Open” events.
Problem to solve
When a user subscribes to an issue or MR, they may solely wish to know when its tracked problem has been remediated, rather than exactly how.
Intended users
Managers supervising significant amounts of issues, and the less technical.
User experience goal
Reduce the amount of undesirable e-mail notifications.
Proposal
Permit users to subscribe solely to:
-
Issues
-
[Re-]closure
-
[Re-]openage
-
-
MRs/PRs
-
The aforementioned
-
Merge
-
Drafthood
-
Further details
This should reduce the amount of unnecessary mail a subscriber receives when they merely wish to be notified when an issue is solved.
Permissions and Security
Users of any permission level should be able to access this.
Documentation
Documentation should follow GitHub's.
Available Tier
Free
Feature Usage Metrics
I have no experience in this, but it should be tracked.
What does success look like, and how can we measure that?
When a user is able to customise their subscription per-issue to encompass certain types of events, this has been solved.
What is the type of buyer?
Anyone tracking the implementation of a significant mount of, or very noisy, features, but not how they are implemented.
Is this a cross-stage feature?
Yes. It should affect any group which utilises issues.
What is the competitive advantage or differentiation for this feature?
It significantly reduces the burden on e-mail servers which handle subscriptions.
Links / references
Per github.com/go-gitea/gitea/issues/22920:
Requested At