diff --git a/assets/images/help/repository/code-scanning-alert-details.png b/assets/images/help/repository/code-scanning-alert-details.png
index 4369d5249b..4fc357cfda 100644
Binary files a/assets/images/help/repository/code-scanning-alert-details.png and b/assets/images/help/repository/code-scanning-alert-details.png differ
diff --git a/assets/images/help/repository/code-scanning-alert-development-section.png b/assets/images/help/repository/code-scanning-alert-development-section.png
new file mode 100644
index 0000000000..e924b04be8
Binary files /dev/null and b/assets/images/help/repository/code-scanning-alert-development-section.png differ
diff --git a/assets/images/help/repository/code-scanning-alert-without-development.png b/assets/images/help/repository/code-scanning-alert-without-development.png
new file mode 100644
index 0000000000..9cca8fa61d
Binary files /dev/null and b/assets/images/help/repository/code-scanning-alert-without-development.png differ
diff --git a/assets/images/help/repository/code-scanning-alert.png b/assets/images/help/repository/code-scanning-alert.png
index 9cca8fa61d..063c886bdd 100644
Binary files a/assets/images/help/repository/code-scanning-alert.png and b/assets/images/help/repository/code-scanning-alert.png differ
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md b/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md
index de23db3b62..93f68bbea2 100644
--- a/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md
+++ b/content/code-security/code-scanning/managing-code-scanning-alerts/about-code-scanning-alerts.md
@@ -50,8 +50,20 @@ Each alert highlights a problem with the code and the name of the tool that iden
 
 {% data reusables.code-scanning.alert-default-branch %}
 
+{% ifversion code-scanning-alert-development-section %}
+
 ![Screenshot of a {% data variables.product.prodname_code_scanning %} alert, includes the alert title, relevant lines of code at the left, metadata at the right.](/assets/images/help/repository/code-scanning-alert.png)
 
+You can also view affected branches, as well as fixes and associated pull requests for an alert. This helps you and your team stay informed about the progress of fixing alerts.
+
+![Screenshot of the "Development" section of a {% data variables.product.prodname_code_scanning %} alert, includes a title of a pull request that could fix the alert.](/assets/images/help/repository/code-scanning-alert-development-section.png)
+
+{% else %}
+
+![Screenshot of a {% data variables.product.prodname_code_scanning %} alert, includes the alert title, relevant lines of code at the left, metadata at the right.](/assets/images/help/repository/code-scanning-alert-without-development.png)
+
+{% endif %}
+
 If you configure {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
 
 When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_caps %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
diff --git a/content/code-security/code-scanning/managing-code-scanning-alerts/code-scanning-alert-development-section.png b/content/code-security/code-scanning/managing-code-scanning-alerts/code-scanning-alert-development-section.png
new file mode 100644
index 0000000000..b37347448f
Binary files /dev/null and b/content/code-security/code-scanning/managing-code-scanning-alerts/code-scanning-alert-development-section.png differ
diff --git a/data/features/code-scanning-alert-development-section.yml b/data/features/code-scanning-alert-development-section.yml
new file mode 100644
index 0000000000..91e88f376b
--- /dev/null
+++ b/data/features/code-scanning-alert-development-section.yml
@@ -0,0 +1,5 @@
+# Reference: #16275
+versions:
+  ghec: '*'
+  fpt: '*'
+  ghes: '>3.17'
diff --git a/data/reusables/code-scanning/alert-default-branch.md b/data/reusables/code-scanning/alert-default-branch.md
index aa1e79fd15..46c64f977b 100644
--- a/data/reusables/code-scanning/alert-default-branch.md
+++ b/data/reusables/code-scanning/alert-default-branch.md
@@ -1 +1 @@
-The status and details on the alert page only reflect the state of the alert on the default branch of the repository, even if the alert exists in other branches. You can see the status of the alert on non-default branches in the **Affected branches** section on the right-hand side of the alert page. If an alert doesn't exist in the default branch, the status of the alert will display as "in pull request" or "in branch" and will be colored grey.
+The status and details on the alert page only reflect the state of the alert on the default branch of the repository, even if the alert exists in other branches. You can see the status of the alert on non-default branches in the **Affected branches** section on the right-hand side of the alert page. If an alert doesn't exist in the default branch, the status of the alert will display as "in pull request" or "in branch" and will be colored grey. The **Development** section shows linked branches and pull requests that will fix the alert.