Separate Configuration of Comments on Pull Requests vs Comments on Issues

[0xCLARITY]

Based on the documentation here, you can only configure notifications for new comments on both PRs AND issues simultaneously.

It would be useful if notifications for PR comments could be configured separately from issue comments.

This is similar to #420, but different, because that issue is about separating configuration of PR top-level comments from individual comments on lines of code. This issue about splitting the comment configuration for issues from notifcations on PR comments.

[stale]

Is this still relevant? If so, just comment with any updates and we'll leave it open. Otherwise, if there is no further activity, it will be closed.

[0xCLARITY]

Still relevant.

[Startouf]

I confirm this issue is very relevant.

In my team, we have a

• #tech channel where we mostly manage PR reviews and everything code-related (only Tech guys in there) so from a developer point of view
• #running-kanban channel which is used to notify our larger (Tech + Product team) of all changes / comments on features (issues) from a product point of view (requirements, etc.).

So we'd basically like to register only issue comments in #running-kanban, and only PR comments in #tech

[burakalver]

I confirm this issue is very relevant.

We would like to only be notified about comments on issues but not PRs.

[mverma16]

Our team is also looking for distinct comments for PRs and issues. We use different channels to get updates from issues and PRs on our repository. Current event subscription for comments posts comments on both #PR and #issues on commenting on any of PR/issues. It sometimes results in unnecessary noise in both of our channels.