Skip to content

Massive number of personal notifications about "re-scoping" PRs #344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yan-uvarovsky opened this issue Feb 6, 2024 · 2 comments
Closed
Labels
bitbucket bug Something isn't working

Comments

@yan-uvarovsky
Copy link

yan-uvarovsky commented Feb 6, 2024

After upgrading plugin version from 4.0.8 to 4.0.9 developers started to receive a lot of personal notifications in Slack for "pull request re-scoped" events.
It looks like that every commit to repository triggers something called "re-scope" of each PR in BitBucket Server and every such event leads to a separate notification. If you have 30 PRs open for a given repo each developer will receive 30 Slack notifications for every push to this repository:
image

There is no dedicated toggle for this event in BitBucket UI:
image

We had to roll back to 4.0.8.
We use Atlassian Bitbucket v7.21.21

@mvlasovatl mvlasovatl added bug Something isn't working bitbucket labels Feb 8, 2024
@mvlasovatl
Copy link
Contributor

Oh it must be caused by #277 . Please roll back to 4.0.8 while we are working on fix.

yevhenhr added a commit that referenced this issue May 16, 2024
#344 Ignore RESCOPED event without any changes to target PR
@yevhenhr
Copy link
Collaborator

Version 4.0.10 with a fix to this issue is available on the Marketplace
Bitbucket Data Center for Slack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bitbucket bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants