ref(releases): fix issue count on release index & other spots #99555
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michellewzhang
changed the title
github-actions
bot
added
the
Scope: Frontend
michellewzhang
changed the title
|
✅ All tests passed |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
michellewzhang
changed the title
cmanallen
approved these changes
Sep 16, 2025
liuirene256
pushed a commit
that referenced
this pull request
Sep 16, 2025
closes https://linear.app/getsentry/issue/REPLAY-706/release-newgroups-count-is-sometimes-incorrect closes https://linear.app/getsentry/issue/REPLAY-151/release-overview-new-issues-counter-doesnt-filter-when-selecting closes https://linear.app/getsentry/issue/REPLAY-139/new-issues-in-release-showing-up-unexpectedly-in-the-team-plan i believe all the issues above were relating to an incorrect issue count value in the release row, leading to confusion about the actual count of new issues for that release. the `newGroups` value returned by the `/releases/` endpoint is correct; however, the frontend on the releases index was mistakenly using the project's `newGroups` field. The project's `newGroups` field is the sum of all the new issues for that project -- hence why they're all the same in the photo below. we should instead be using the count from the release itself. i also fixed 2 other spots where we were relying on the project `newGroups` field in insights mobile session health page & on release drawer. before: <img width="1084" height="376" alt="SCR-20250915-nxra" src="https://github.com/user-attachments/assets/2f2044b7-4cb2-49e1-b2fb-437589bf0212" /> <img width="1272" height="514" alt="SCR-20250915-oech" src="https://github.com/user-attachments/assets/d6b7d321-c91b-4221-a673-bdc2656c40a5" /> after: <img width="1080" height="346" alt="SCR-20250915-nxnn" src="https://github.com/user-attachments/assets/a72f03fd-e478-4e22-a6c8-217958674cfc" /> <img width="1267" height="564" alt="SCR-20250915-ocyn" src="https://github.com/user-attachments/assets/65364c90-f9de-459a-af16-82ab1313fdd8" />
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes https://linear.app/getsentry/issue/REPLAY-706/release-newgroups-count-is-sometimes-incorrect
closes https://linear.app/getsentry/issue/REPLAY-151/release-overview-new-issues-counter-doesnt-filter-when-selecting
closes https://linear.app/getsentry/issue/REPLAY-139/new-issues-in-release-showing-up-unexpectedly-in-the-team-plan
i believe all the issues above were relating to an incorrect issue count value in the release row, leading to confusion about the actual count of new issues for that release.
the
newGroupsvalue returned by the/releases/endpoint is correct; however, the frontend on the releases index was mistakenly using the project'snewGroupsfield. The project'snewGroupsfield is the sum of all the new issues for that project -- hence why they're all the same in the photo below. we should instead be using the count from the release itself.i also fixed 2 other spots where we were relying on the project
newGroupsfield in insights mobile session health page & on release drawer.before:
after:
