feat(releases): Team insights docs after issue / health stats split (#4712)

* feat(releases): Team insights docs after issue / health stats split

* copy updates, image updates

* added quotes for consistency

* style fix

* rename usage-stats png

* rename usage-stats png 2

* anchors

Co-authored-by: robinrendle <robinjrendle@gmail.com>
Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com>

Author: 3 people

src/docs/product/stats/health-stats.png

@@ -2,17 +2,17 @@
 title: Stats
 sidebar_order: 20
 redirect_from:
-- /product/accounts/quotas/org-stats/
+  - /product/accounts/quotas/org-stats/
 description: "Learn about projects and teams across your organization."
 ---
 
-The **Stats** page has two tabs: [Usage Stats](#usage-stats) and [Team Stats](#team-stats).
+The **Stats** page has three tabs: [Usage](#usage-stats), [Issues](#issue-stats), and [Health](#health-stats).
 
-The "Usage Stats" tab shows your organization’s event usage, while also providing a high-level overview of how different projects are using Sentry. The "Team Stats" tab, on the other hand, gives you insights into how your team is using Sentry — for example, it shows you how many issues your team has reviewed and the number of releases they’ve shipped — as well as giving you an overview of the health of your projects.
+The "Usage" tab shows your organization’s event usage, while also providing a high-level overview of how different projects are using Sentry. The "Issues" tab shows a breakdown of the issues assigned to your team and how they triaged them, whilst the "Health" tab provides an overview of your team’s project health.
 
-## Usage Stats
+## Usage Stats {#usage-stats}
 
-The "Usage Stats" tab shows you the events Sentry has received across your entire organization along with a list of all projects and their consumption of errors, transactions, and attachments. Events fall into one of three categories: _Accepted_, _Filtered_, or _Dropped_. Filtered events are events that were blocked due to your [inbound data filter](/product/data-management-settings/filtering/) rules. Dropped events are ones the system dropped or discarded due to rate limits, quotas, spike protection, or because of invalid data.
+The "Usage" tab shows you the events Sentry has received across your entire organization along with a list of all projects and their consumption of errors, transactions, and attachments. Events fall into one of three categories: _Accepted_, _Filtered_, or _Dropped_. Filtered events are events that were blocked due to your [inbound data filter](/product/data-management-settings/filtering/) rules. Dropped events are ones the system dropped or discarded due to rate limits, quotas, spike protection, or because of invalid data.
 
 You can see which projects have had a recent spike or are the most active and may need more attention. On this page, you can also control the date range that’s displayed, allowing you to focus on a smaller period of time or zoom out for a longer view. The page is designed for org admins, but is available to all team members. This is helpful if a team member who isn't an admin is tasked with reviewing these statistics. Also, this allows team members associated with specific projects to use this page to investigate why their events are being dropped.
 
@@ -21,9 +21,7 @@ You can see which projects have had a recent spike or are the most active and ma
 With the dropdowns at the top of the page, you can set whether the page displays stats for errors, transactions, or attachments, as well as the date range. With the date selector, the time period can be set from an hour to a maximum of 90 days, and all of the page elements change dynamically when you update this setting.
 
 <Note>
-
-This page does not include data about sessions because they are not a billable event type.
-
+  This page does not include data about sessions because they are not a billable event type.
 </Note>
 
 ### Usage Cards
@@ -44,65 +42,57 @@ Each project in the table has individual settings, which you can access from by
 
 The table displays only the projects of the teams that you belong to, unless you have permissions to see all projects.
 
-## Team Stats
+## Issues Stats {#issue-stats}
 
 <Note>
-
   This feature is available only if your organization is on a Business plan.
-
-</Note>
-
-<Note>
-
-  This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony.
-  If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
-
 </Note>
 
-In the "Team Stats" tab you can review information about the overall health of your projects and see how your team is using Sentry. At the top of this page, you can select a team, which will filter the metrics shown below. The default time range for team stats is the last eight weeks, which allows you to compare changes week by week. The team stats are divided into two sections: [Project Health](#project-health) and [Team Activity](#team-activity).
+The "Issues" tab shows activity about issues assigned to your team; how many new issues were detected, how many resolved issues regressed, and how they were triaged.
 
-![Overview of Usage Stats page](team-stats.png)
+![The Issues Stats page](issues-stats.png)
 
-### Project Health
-
-The "Project Health" section of your team stats provides an overview of your application and shows you a summary of your projects’ Crash Free Rate, as well the User Misery of your team’s key transactions. This gives you a quick idea of which projects and key transactions might need attention from your team. In this section, you can also view how many alerts have been triggered from the metric alerts your team owns.
+#### All Unresolved Issues
 
-#### Crash Free Sessions
+The "All Unresolved Issues" chart and table show new and returning issues per project in the last seven days, as well as those that haven’t been resolved or ignored in the past.
 
-The "Crash Free Sessions" table shows the percentage of sessions that didn’t cause a crash for the selected date range.
+#### New and Returning Issues
 
-#### User Misery
+The "New and Returning Issues" chart and table show the new, regressed, and unignored issues that were assigned to your team.
 
-The "User Misery" table shows transactions where users experienced load times four times the project’s configured threshold, with the number of unique users for each of those transactions.
+#### Issues Triaged
 
-#### Metric Alerts Triggered
+The "Issues Triaged" chart and table show how many new and returning issues were reviewed by your team each week. Reviewing an issue includes marking it as reviewed, resolving it, assigning it to another team, or deleting it.
 
-The "Metric Alerts Triggered" chart and table show alert rules that have been triggered for the projects your team owns.
+#### Age of Unresolved Issues
 
+The "Age of Unresolved Issues" chart and table show how long ago the oldest seven unresolved issues were first created for the projects your team owns, sorted by their age.
 
-### Team Activity
+#### Time to Resolution
 
-The "Team Activity" section of your team stats shows how many issues have been reviewed, including a breakdown per project. It also reveals the mean time it took to resolve issues, as well as the number of releases that have been created in the projects that your team owns.
+The "Time to Resolution" chart shows the mean time it took for issues to be resolved by your team each week.
 
-#### New and Returning Issues
+## Health Stats {#health-stats}
 
-The "New and Returning Issues" chart and table show the new, regressed, and unignored issues that were assigned to your team.
+<Note>
+  This feature is available only if your organization is on a Business plan.
+</Note>
 
-#### Issues Triaged
+The "Health" tab shows information about the overall health of your projects; the crash free sessions, user misery of your team’s key transactions, the number of alerts triggered by your team’s alert rules, and the number of releases per project.
 
-The "Issues Triaged" chart and table show how many new and returning issues were reviewed by your team each week. Reviewing an issue includes marking it as reviewed, resolving it, assigning it to another team, or deleting it.
+![The Health Stats page](health-stats.png)
 
-#### Age of Unresolved Issues
+#### Crash Free Sessions
 
-The "Age of Unresolved Issues" chart and table show how long ago the oldest seven unresolved issues were first created for the projects your team owns, sorted by their age.
+The "Crash Free Sessions" table shows the percentage of sessions that didn’t cause a crash for the selected date range.
 
-#### All Unresolved Issues
+#### User Misery
 
-The "All Unresolved Issues" chart and table show new and returning issues per project in the last seven days, as well as those that haven’t been resolved or ignored in the past.
+The "User Misery" table shows transactions where users experienced load times four times the project’s configured threshold, with the number of unique users for each of those transactions.
 
-#### Time to Resolution
+#### Metric Alerts Triggered
 
-The "Time to Resolution" chart shows the mean time it took for issues to be resolved by your team each week.
+The "Metric Alerts Triggered" chart and table show alert rules that have been triggered for the projects your team owns.
 
 #### Number of Releases