fix(releases): Fix new groups count per project for a release #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally, the number of new groups per project for a certain release was incorrect - it showed the same number for all projects in a release. This is because we were using the per-project new groups count (ie, release.projects[x].newGroups), which was incorrectly returning the sum of all new group counts across all releases for that project.
In getsentry#99555 we switched to using release.newGroups. But this also incorrectly returns the total number of new issues across all projects for that release.
Here we fix the underlying issue with release.projects[x].newGroups by setting it to the new groups count for that release in that project. This fix only applies to the new serializer.
Copied from getsentry#100919
Original PR: getsentry#100919