Michael Kochell

> @sanjaydemansol If you want to get into graphql, wrapping up #404 might be a good starting point. @hanzei Yes that PR should probably be merged before any other work...

https://developers.mattermost.com/integrate/plugins/server/reference/#Hooks.ReactionHasBeenAdded https://developers.mattermost.com/integrate/plugins/server/reference/#Hooks.ReactionHasBeenRemoved

@hanzei There's an issue here @sibasankar-demansol ran into where the OAuth token does not have permissions to create webhooks. We currently request the scopes: - repo - notifications - read:org...

@sanjaydemansol @maisnamrajusingh For any requests you've made on this PR that have been fulfilled, please click "Resolve Conversation" at the bottom of the request's discussion

@hanzei I'm seeing this feature as an opportunity to support multiple webhook secrets. There was recently a request for this functionality. https://community-daily.mattermost.com/core/pl/uf5fzfmu97bbfqfw1qgjjebh4h Out of scope of this PR, but if...

There are a lot of unresolved comments on this PR. @sanjaydemansol @maisnamrajusingh Can you please resolve the conversations for any requests you've made on this PR that have been fulfilled?...

I think we should add two new flags for subscriptions: - `only_confidential` - `exclude_confidential` The default behavior will still deliver both regular and confidential issues.

Note that in order to properly support this, we will need to have a new plugin hook `UserHasBeenDeactivated`

@hanzei To comply with GDPR, we should clean up this information when the user disconnects their account. Note that I'm basing this off of Atlassian's policy https://developer.atlassian.com/cloud/jira/platform/user-privacy-developer-guide/#storing-user-personal-data-for-your-apps

@dimashasbi You will need to add a new plugin hook to the plugin framework as the first part of this task. You can see in https://github.com/mattermost/mattermost-server how this is done,...