Proposal: Add "issue subscriptions" to manage notification logic

Overview

As described in the wiki page, notifications are sent out to specified users when an event occurs. This contrasts current GitHub functionality which has the concept of subscriptions to determine who is notified.

I propose that we introduce the concept of subscriptions to issues in Gitbucket. For the purposes of this proposal, the term issues includes pull requests

Subscribing

At issue creation, the following users will be auto-subscribed:

• Repository owner and collaborators
• Issue creator
• Repository watchers (if implemented in the future)

Additionally, the following events will auto-subscribe a user:

• Issue assignment
• @-mentions

Finally, any user can subscribe or unsubscribe to an issue via a new UI element to be added on the view issue page. This UI element only appears for logged-in users

Sending Notifications

All subscribers to an issue will receive a notification for the following events:

• Issue creation
• Comment creation
• Status update

Exception to above: the user who initiates the action will not receive a notification

Database Table

Issue subscriptions will be tracked in a new table

ISSUE_SUBSCRIPTION

• USER_ID
• REPOSITORY_NAME
• ISSUE_ID
• SUBSCRIBER_USER_NAME
• REASON - e.g. author, owner, assigned, subscribed, mentioned, collaborator, watcher

UI Mockup

Example Subscribe UI	Example Unsubscribe UI

[takezoe]

gitbucket-notifications-plugin will be bundled in default since GitBucket 4.15.0

[marklacroix]

Thanks guys. Looking forward to having this available in 4.15. Keep up the amazing work!