From 42c1f8ebc5272906936d1f128bcecbed3e05a6d4 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 31 Oct 2023 09:24:27 -0600
Subject: [PATCH 01/33] Update home.html

---
 src/registrar/templates/home.html | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index e86c08c70..730430ffd 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -13,7 +13,11 @@
   <h1>Manage your domains</h2>
 
   <p class="margin-top-4">
-    <a href="{% url 'application:' %}" class="usa-button">
+    <a href="{% url 'application:' %}" 
+    class="usa-button usa-tooltip disabled-link"
+    data-position="right"
+    title="Coming in 2024"
+    >
       Start a new domain request
     </a>
   </p>

From 6e34d231f30d50ea57cd355ae5c910a598238a72 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Fri, 3 Nov 2023 09:37:10 -0600
Subject: [PATCH 02/33] Add global setting

---
 ops/manifests/manifest-za.yaml    | 3 +++
 src/registrar/config/settings.py  | 3 +++
 src/registrar/templates/home.html | 8 +++++++-
 src/registrar/views/index.py      | 3 ++-
 4 files changed, 15 insertions(+), 2 deletions(-)

diff --git a/ops/manifests/manifest-za.yaml b/ops/manifests/manifest-za.yaml
index 23b6179ec..774ed57ec 100644
--- a/ops/manifests/manifest-za.yaml
+++ b/ops/manifests/manifest-za.yaml
@@ -23,6 +23,9 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # NOTE: This needs to go in manifest-staging
+    # This is here for PR purposes only!
+    IS_PRODUCTION: True
   routes:
     - route: getgov-za.app.cloud.gov
   services:
diff --git a/src/registrar/config/settings.py b/src/registrar/config/settings.py
index 3e5734dcc..99c0add33 100644
--- a/src/registrar/config/settings.py
+++ b/src/registrar/config/settings.py
@@ -46,6 +46,7 @@ path = Path(__file__)
 
 env_db_url = env.dj_db_url("DATABASE_URL")
 env_debug = env.bool("DJANGO_DEBUG", default=False)
+env_is_production = env.bool("IS_PRODUCTION", default=False) 
 env_log_level = env.str("DJANGO_LOG_LEVEL", "DEBUG")
 env_base_url = env.str("DJANGO_BASE_URL")
 env_getgov_public_site_url = env.str("GETGOV_PUBLIC_SITE_URL", "")
@@ -72,6 +73,8 @@ BASE_DIR = path.resolve().parent.parent.parent
 # SECURITY WARNING: don't run with debug turned on in production!
 DEBUG = env_debug
 
+# Controls production specific feature toggles
+IS_PRODUCTION = env_is_production
 
 # Applications are modular pieces of code.
 # They are provided by Django, by third-parties, or by yourself.
diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index 730430ffd..ff487dc06 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -13,6 +13,7 @@
   <h1>Manage your domains</h2>
 
   <p class="margin-top-4">
+    {% if is_production %}
     <a href="{% url 'application:' %}" 
     class="usa-button usa-tooltip disabled-link"
     data-position="right"
@@ -20,6 +21,11 @@
     >
       Start a new domain request
     </a>
+    {% else %}
+    <a href="{% url 'application:' %}" class="usa-button">
+      Start a new domain request
+    </a>
+    {% endif %}
   </p>
 
   <section class="section--outlined tablet:grid-col-11 desktop:grid-col-10">
@@ -134,7 +140,7 @@
     {% endif %}
   </section>
 
-  {# Note: Reimplement this after MVP.. #}
+  {# Note: Reimplement this after MVP #}
   <!--
   <section class="section--outlined tablet:grid-col-11 desktop:grid-col-10">
     <h2>Archived domains</h2>
diff --git a/src/registrar/views/index.py b/src/registrar/views/index.py
index b203694ff..7d351b417 100644
--- a/src/registrar/views/index.py
+++ b/src/registrar/views/index.py
@@ -2,7 +2,7 @@ from django.db.models import F
 from django.shortcuts import render
 
 from registrar.models import DomainApplication
-
+from django.conf import settings
 
 def index(request):
     """This page is available to anyone without logging in."""
@@ -22,4 +22,5 @@ def index(request):
             state=F("domain__state"),
         )
         context["domains"] = domains
+        context["is_production"] = settings.IS_PRODUCTION
     return render(request, "home.html", context)

From 228fcaea6534fdb57e727ac5597544879d255911 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Fri, 3 Nov 2023 09:44:09 -0600
Subject: [PATCH 03/33] Update home.html

---
 src/registrar/templates/home.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index ff487dc06..b5e46aaf8 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -15,7 +15,7 @@
   <p class="margin-top-4">
     {% if is_production %}
     <a href="{% url 'application:' %}" 
-    class="usa-button usa-tooltip disabled-link"
+    class="usa-button usa-tooltip disabled-domain-request-link"
     data-position="right"
     title="Coming in 2024"
     >

From 3224d41c33ec7a8e8d4998df6be01dd1da3a323b Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Fri, 3 Nov 2023 14:10:03 -0600
Subject: [PATCH 04/33] Add styling and preferential link logic

---
 src/registrar/assets/sass/_theme/_buttons.scss | 6 ++++++
 src/registrar/templates/home.html              | 5 +++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/src/registrar/assets/sass/_theme/_buttons.scss b/src/registrar/assets/sass/_theme/_buttons.scss
index cb2117fb9..c8153851a 100644
--- a/src/registrar/assets/sass/_theme/_buttons.scss
+++ b/src/registrar/assets/sass/_theme/_buttons.scss
@@ -26,6 +26,12 @@ a.usa-button {
   text-decoration: none;
 }
 
+a.usa-button.disabled-link {
+  pointer-events: none !important;
+  cursor: default !important;
+  background-color: #ccc !important;
+}
+
 a.usa-button:not(.usa-button--unstyled, .usa-button--outline) {
   color: color('white');
 }
diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index b5e46aaf8..114b58a91 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -15,14 +15,15 @@
   <p class="margin-top-4">
     {% if is_production %}
     <a href="{% url 'application:' %}" 
-    class="usa-button usa-tooltip disabled-domain-request-link"
+    class="usa-button usa-tooltip disabled-link"
     data-position="right"
     title="Coming in 2024"
     >
       Start a new domain request
     </a>
     {% else %}
-    <a href="{% url 'application:' %}" class="usa-button">
+    <a href="{% url 'application:' %}" class="usa-button"
+    >
       Start a new domain request
     </a>
     {% endif %}

From 3b186509c1e6c5f82bd4d05945da4fd6b63056e1 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Fri, 3 Nov 2023 14:24:31 -0600
Subject: [PATCH 05/33] Additional hover styling

---
 src/registrar/assets/sass/_theme/_buttons.scss | 7 ++++++-
 src/registrar/config/settings.py               | 2 +-
 src/registrar/views/index.py                   | 1 +
 3 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/src/registrar/assets/sass/_theme/_buttons.scss b/src/registrar/assets/sass/_theme/_buttons.scss
index c8153851a..de7a280e6 100644
--- a/src/registrar/assets/sass/_theme/_buttons.scss
+++ b/src/registrar/assets/sass/_theme/_buttons.scss
@@ -27,11 +27,16 @@ a.usa-button {
 }
 
 a.usa-button.disabled-link {
-  pointer-events: none !important;
   cursor: default !important;
   background-color: #ccc !important;
 }
 
+a.usa-button.disabled-domain-request-link:hover {
+  color: #ccc !important;
+  cursor: not-allowed !important;
+  text-decoration: none !important;
+}
+
 a.usa-button:not(.usa-button--unstyled, .usa-button--outline) {
   color: color('white');
 }
diff --git a/src/registrar/config/settings.py b/src/registrar/config/settings.py
index 99c0add33..9e14f1568 100644
--- a/src/registrar/config/settings.py
+++ b/src/registrar/config/settings.py
@@ -46,7 +46,7 @@ path = Path(__file__)
 
 env_db_url = env.dj_db_url("DATABASE_URL")
 env_debug = env.bool("DJANGO_DEBUG", default=False)
-env_is_production = env.bool("IS_PRODUCTION", default=False) 
+env_is_production = env.bool("IS_PRODUCTION", default=False)
 env_log_level = env.str("DJANGO_LOG_LEVEL", "DEBUG")
 env_base_url = env.str("DJANGO_BASE_URL")
 env_getgov_public_site_url = env.str("GETGOV_PUBLIC_SITE_URL", "")
diff --git a/src/registrar/views/index.py b/src/registrar/views/index.py
index 7d351b417..93a1119c2 100644
--- a/src/registrar/views/index.py
+++ b/src/registrar/views/index.py
@@ -4,6 +4,7 @@ from django.shortcuts import render
 from registrar.models import DomainApplication
 from django.conf import settings
 
+
 def index(request):
     """This page is available to anyone without logging in."""
     context = {}

From e1d85c15caf745781d80469fbb33a7ecee4b550c Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Fri, 3 Nov 2023 14:37:13 -0600
Subject: [PATCH 06/33] Additional styles

---
 src/registrar/assets/sass/_theme/_buttons.scss | 11 +++++++++--
 src/registrar/templates/home.html              |  2 +-
 2 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/src/registrar/assets/sass/_theme/_buttons.scss b/src/registrar/assets/sass/_theme/_buttons.scss
index de7a280e6..ec9f03012 100644
--- a/src/registrar/assets/sass/_theme/_buttons.scss
+++ b/src/registrar/assets/sass/_theme/_buttons.scss
@@ -27,14 +27,21 @@ a.usa-button {
 }
 
 a.usa-button.disabled-link {
-  cursor: default !important;
   background-color: #ccc !important;
 }
 
-a.usa-button.disabled-domain-request-link:hover {
+a.usa-button.disabled-link:hover {
   color: #ccc !important;
   cursor: not-allowed !important;
   text-decoration: none !important;
+  
+}
+
+a.usa-button.disabled-link:focus {
+  color: #ccc !important;
+  cursor: not-allowed !important;
+  text-decoration: none !important;
+  outline: none !important;
 }
 
 a.usa-button:not(.usa-button--unstyled, .usa-button--outline) {
diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index 114b58a91..a00ab71c4 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -14,7 +14,7 @@
 
   <p class="margin-top-4">
     {% if is_production %}
-    <a href="{% url 'application:' %}" 
+    <a href="event.stopPropagation();" 
     class="usa-button usa-tooltip disabled-link"
     data-position="right"
     title="Coming in 2024"

From a035d06569f019707a85ae32854fa22d04b10faf Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Fri, 3 Nov 2023 14:45:08 -0600
Subject: [PATCH 07/33] Fix issue

---
 .gitignore                                     | 11 +++++++++++
 src/registrar/assets/sass/_theme/_buttons.scss |  7 ++-----
 src/registrar/templates/home.html              |  2 +-
 3 files changed, 14 insertions(+), 6 deletions(-)

diff --git a/.gitignore b/.gitignore
index a4df194fa..aa78024cb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -171,3 +171,14 @@ node_modules
 
 # Compliance/trestle related
 docs/compliance/.trestle/cache
+src/migrationdata/20231009.agency.adhoc.dotgov.txt
+src/migrationdata/20231009.authority.adhoc.dotgov.txt
+src/migrationdata/20231009.domainadditionaldatalink.adhoc.dotgov.txt
+src/migrationdata/20231009.domaindocumentdatalink.adhoc.dotgov.txt
+src/migrationdata/20231009.domaintypes.adhoc.dotgov.txt
+src/migrationdata/20231009.organization.adhoc.dotgov.txt
+src/migrationdata/escrow_contacts.daily.dotgov.GOV.txt
+src/migrationdata/escrow_domain_contacts.daily.dotgov.GOV.txt
+src/migrationdata/escrow_domain_statuses.daily.dotgov.GOV.txt
+src/migrationdata/escrow_domains.daily.dotgov.GOV.txt
+src/migrationdata/scriptstuff.tar.gz
diff --git a/src/registrar/assets/sass/_theme/_buttons.scss b/src/registrar/assets/sass/_theme/_buttons.scss
index ec9f03012..2f85bc542 100644
--- a/src/registrar/assets/sass/_theme/_buttons.scss
+++ b/src/registrar/assets/sass/_theme/_buttons.scss
@@ -31,16 +31,13 @@ a.usa-button.disabled-link {
 }
 
 a.usa-button.disabled-link:hover {
-  color: #ccc !important;
+  background-color: #ccc !important;
   cursor: not-allowed !important;
-  text-decoration: none !important;
-  
 }
 
 a.usa-button.disabled-link:focus {
-  color: #ccc !important;
+  background-color: #ccc !important;
   cursor: not-allowed !important;
-  text-decoration: none !important;
   outline: none !important;
 }
 
diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index a00ab71c4..f23fd9a6d 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -14,7 +14,7 @@
 
   <p class="margin-top-4">
     {% if is_production %}
-    <a href="event.stopPropagation();" 
+    <a href="javascript:void(0)" 
     class="usa-button usa-tooltip disabled-link"
     data-position="right"
     title="Coming in 2024"

From 350b6d4a07907ccb9ca3789720f8d4ee9ab532c8 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Fri, 3 Nov 2023 15:21:20 -0600
Subject: [PATCH 08/33] Remove temp gitignore changes

---
 .gitignore | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/.gitignore b/.gitignore
index aa78024cb..a4df194fa 100644
--- a/.gitignore
+++ b/.gitignore
@@ -171,14 +171,3 @@ node_modules
 
 # Compliance/trestle related
 docs/compliance/.trestle/cache
-src/migrationdata/20231009.agency.adhoc.dotgov.txt
-src/migrationdata/20231009.authority.adhoc.dotgov.txt
-src/migrationdata/20231009.domainadditionaldatalink.adhoc.dotgov.txt
-src/migrationdata/20231009.domaindocumentdatalink.adhoc.dotgov.txt
-src/migrationdata/20231009.domaintypes.adhoc.dotgov.txt
-src/migrationdata/20231009.organization.adhoc.dotgov.txt
-src/migrationdata/escrow_contacts.daily.dotgov.GOV.txt
-src/migrationdata/escrow_domain_contacts.daily.dotgov.GOV.txt
-src/migrationdata/escrow_domain_statuses.daily.dotgov.GOV.txt
-src/migrationdata/escrow_domains.daily.dotgov.GOV.txt
-src/migrationdata/scriptstuff.tar.gz

From ee7bfc973dc8ebd1ae2f3f9ecb7e032d4e79bda3 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Mon, 6 Nov 2023 10:58:06 -0700
Subject: [PATCH 09/33] Update manifest-stable.yaml

---
 ops/manifests/manifest-stable.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/ops/manifests/manifest-stable.yaml b/ops/manifests/manifest-stable.yaml
index 6295fa63b..69e86cf0b 100644
--- a/ops/manifests/manifest-stable.yaml
+++ b/ops/manifests/manifest-stable.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: True
   routes:
     - route: getgov-stable.app.cloud.gov
   services:

From 7bc1c008b177f9e94ac06bce1ea6b86625f7f008 Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Mon, 6 Nov 2023 10:15:38 -0800
Subject: [PATCH 10/33] added bug handling/ triaging readme

---
 docs/product/product_strategy.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/docs/product/product_strategy.md b/docs/product/product_strategy.md
index 1a17727d1..f6c665210 100644
--- a/docs/product/product_strategy.md
+++ b/docs/product/product_strategy.md
@@ -22,3 +22,27 @@ CISA lacks a scalable, efficient, and secure method of managing the .gov TLD pro
 | **Data:** The program maintains authoritative contacts at, metadata about, and hostname information for all registered .gov domains, and is able to track that .gov domains are actually used | - Time-to-generate internal reports decreases <br /> - Results of periodic data quality audit show improvements month-over-month                                                                              |
 | **User satisfaction:** Getting a .gov domain is as easy and intuitive as possible                                                                                                             | - Completion rate of form improves <br /> - Time from domain request to approval decreases <br /> - Number of domains requiring analyst data changes decreases                                                        |
 | **Program reputation and experience:** The .gov program is viewed as trustworthy and responsive                                                                                               | - Response time for inquiries decreases <br /> - Resolution time decreases <br /> - Rate of repeat issues for tickets decreases <br /> - Number of SLTT organizations in Community of Practice increases                                      |
+
+## Bug triage
+
+Bugs on production software need to be documented quickly and triaged to determine if fixes need to be made outside of the normal release cadence. Triage levels will be Critical, High, Medium, and Low to indicate the level of priority for fix, not neccessarily the level of severity. See below for more details
+
+**Critical**- should only be determined by the product owner and means the fix for this _critical_ bug needs to have a quick fix for it created ASAP. This is the only case where a bug fix can be added outside of the normal release cycle and directly onto the stable release.
+**High**- Can be determined by product owner or other team member, and indicates this bug is critical enough to warrant being added into the current sprint.
+**Medium**- Should be added to a sprint coming up but is not blocking users, or enough users to warrant rushing it into a sprint
+**Low**- A minor bug, that could even wait until after the next big launch date to be implemented.
+
+### Steps for Triaging
+
+1. When a bug is found, whether by a developer/designer or from feedback from an end user, a ticket should be made immediately. The actual ticket maker of the ticket can be a member of the product team as needed.
+2. This bug ticket immediately gets a priority added Critical/High/Medium/Low, with Critcal requiring the product owner's request.
+3. Anything marked as critical should be refined immediately and engineering should be notified via Slack that a Critical ticket has been created (if not already notified)
+4. All items not marked as critical by the product owner, should wait until refinement to be refined and may have their prioirty level changed during refinement. 
+
+### Steps for dealing with Critical Bugs
+
+1. Once the critical bug ticket is refined and the bug is clear, an engineer should be assigned to work on it. (No ticket, no work)
+2. At the same point, two other engineers should be assigned to review the PR once it's made. One of the reviewing engineers can be subsititued for a designer if this is a design/content/other user facing bug fix.
+3. In the case where engineering lead is not responsive/ unavailable to assign it immediatley engineers should see the public slack message and volunteer as needed. The product team will be back up to make sure someone is assigned or volunteers for the ticket/PR review ASAP.
+4. Once done the developer, now needs to make a PR as usual but should tagged the assigned PR reviewers in a public slack message that the PR is now waiting on their review. They should drop other tasks in order to review this promptly.
+5. See the Making bug fixes on stable during production readme for how to push changes to stable once the PR is approved

From ecdf52982db169694868e2b4bb50404ed9424325 Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Mon, 6 Nov 2023 10:23:26 -0800
Subject: [PATCH 11/33] fixed typos

---
 docs/product/product_strategy.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/product/product_strategy.md b/docs/product/product_strategy.md
index f6c665210..5ab9b89f8 100644
--- a/docs/product/product_strategy.md
+++ b/docs/product/product_strategy.md
@@ -27,22 +27,22 @@ CISA lacks a scalable, efficient, and secure method of managing the .gov TLD pro
 
 Bugs on production software need to be documented quickly and triaged to determine if fixes need to be made outside of the normal release cadence. Triage levels will be Critical, High, Medium, and Low to indicate the level of priority for fix, not neccessarily the level of severity. See below for more details
 
-**Critical**- should only be determined by the product owner and means the fix for this _critical_ bug needs to have a quick fix for it created ASAP. This is the only case where a bug fix can be added outside of the normal release cycle and directly onto the stable release.
+**Critical**- should only be determined by the product owner and means the fix for this critical bug needs to have a quick fix for it created ASAP. This is the only case where a bug fix can be added outside of the normal release cycle and directly onto the stable release.
 **High**- Can be determined by product owner or other team member, and indicates this bug is critical enough to warrant being added into the current sprint.
 **Medium**- Should be added to a sprint coming up but is not blocking users, or enough users to warrant rushing it into a sprint
 **Low**- A minor bug, that could even wait until after the next big launch date to be implemented.
 
 ### Steps for Triaging
 
-1. When a bug is found, whether by a developer/designer or from feedback from an end user, a ticket should be made immediately. The actual ticket maker of the ticket can be a member of the product team as needed.
+1. When a bug is found, whether by a developer/designer or from feedback from an end user, a ticket should be made immediately. The actual maker of the ticket can be a member of the product team as needed.
 2. This bug ticket immediately gets a priority added Critical/High/Medium/Low, with Critcal requiring the product owner's request.
-3. Anything marked as critical should be refined immediately and engineering should be notified via Slack that a Critical ticket has been created (if not already notified)
-4. All items not marked as critical by the product owner, should wait until refinement to be refined and may have their prioirty level changed during refinement. 
+3. Anything marked as `critical` should be refined immediately and engineering should be notified via Slack that a Critical ticket has been created (if not already notified)
+4. All items not marked as `critical` by the product owner, can wait until refinement to be refined and may have their prioirty level changed during that meeting.
 
 ### Steps for dealing with Critical Bugs
 
 1. Once the critical bug ticket is refined and the bug is clear, an engineer should be assigned to work on it. (No ticket, no work)
 2. At the same point, two other engineers should be assigned to review the PR once it's made. One of the reviewing engineers can be subsititued for a designer if this is a design/content/other user facing bug fix.
-3. In the case where engineering lead is not responsive/ unavailable to assign it immediatley engineers should see the public slack message and volunteer as needed. The product team will be back up to make sure someone is assigned or volunteers for the ticket/PR review ASAP.
-4. Once done the developer, now needs to make a PR as usual but should tagged the assigned PR reviewers in a public slack message that the PR is now waiting on their review. They should drop other tasks in order to review this promptly.
+3. In the case where the engineering lead is not responsive/ unavailable to assign the ticket immediatley, other engineers should see the public slack message and volunteer as needed. The product team will be backup to make sure someone is assigned or volunteers for the ticket/PR review ASAP.
+4. Once done the developer, now needs to make a PR as usual but should tag the assigned PR reviewers in a public slack message stating that the PR is now waiting on their review. These reviewers should drop other tasks in order to review this promptly.
 5. See the Making bug fixes on stable during production readme for how to push changes to stable once the PR is approved

From 625e524d50d621f4af0166eb4e845dd677672108 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Mon, 6 Nov 2023 15:40:13 -0700
Subject: [PATCH 12/33] Fix spacing

---
 .../management/commands/generate_test_transition_domains.py     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/management/commands/generate_test_transition_domains.py b/src/registrar/management/commands/generate_test_transition_domains.py
index 20aba2c58..2865937de 100644
--- a/src/registrar/management/commands/generate_test_transition_domains.py
+++ b/src/registrar/management/commands/generate_test_transition_domains.py
@@ -15,7 +15,7 @@ class Command(BaseCommand):
     # Running this script removes all existing transition domains, so use with caution.
     # Transition domains are created with email addresses provided as command line
     # argument. Email addresses for testing are passed as comma delimited list of
-    # email addresses, and are required to be provided.  Email addresses from the list
+    # email addresses, and are required to be provided. Email addresses from the list
     # are assigned to transition domains at time of creation.
 
     def add_arguments(self, parser):

From 9bf3b3a15f661e7c534c9cb3422be68dc24f1e3d Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Mon, 6 Nov 2023 20:24:48 -0800
Subject: [PATCH 13/33] udpated domain invitation txts

---
 .../emails/transition_domain_invitation.txt   | 52 ++++++++++++++-----
 .../transition_domain_invitation_subject.txt  |  2 +-
 2 files changed, 39 insertions(+), 15 deletions(-)

diff --git a/src/registrar/templates/emails/transition_domain_invitation.txt b/src/registrar/templates/emails/transition_domain_invitation.txt
index 42013dbf7..e97aa322d 100644
--- a/src/registrar/templates/emails/transition_domain_invitation.txt
+++ b/src/registrar/templates/emails/transition_domain_invitation.txt
@@ -1,20 +1,41 @@
 {% autoescape off %}{# In a text file, we don't want to have HTML entities escaped #}
-Hi.
+Hello from .gov.
 
-You have been added as a manager on {% if domains|length > 1 %}multiple domains (listed below){% else %}{{ domains.0 }}{% endif %}.
+Our new domain management system—the .gov registrar—is now available. The organization, contacts, and DNS information for your .gov domain{% if domains|length > 1 %}s{% endif %} have been transferred to our new registrar. 
+
+Your .gov domain{% if domains|length > 1 %}s{% endif %}:
+{% for domain in domains %} - {{ domain }}
+{% endfor %}
+If you’re not affiliated with the above domain{% if domains|length > 1 %}s{% endif %} or think you received this message in error, let us know in a reply to this email. 
+
+
+CREATE A LOGIN.GOV ACCOUNT
+
+You can’t use your old credentials to access the new registrar. Access is now managed through Login.gov, a simple and secure process for signing into many government services with one account. Follow these steps to create your Login.gov account <https://login.gov/help/get-started/create-your-account/>. 
+
+When creating an account, you’ll need to provide the same email address you used to log in to the old registrar. That will ensure your domains are linked to your Login.gov account. 
+
+If you need help finding the email you used in the past, let us know in a reply to this email.
+
+
+CHECK YOUR .GOV DOMAIN CONTACTS
+
+This is a good time to check who has access to your .gov domain{% if domains|length > 1 %}s{% endif %}. The admin, technical, and billing contacts listed for your domain{% if domains|length > 1 %}s{% endif %} in our old system also received this email. However, in our new registrar, these contacts are all considered “domain managers.” We no longer have the admin, technical, and billing roles, and you aren’t limited to three domain managers like in the old system. 
+    1. Once you have your Login.gov account, sign in to the new registrar at <https://manage.get.gov>
+    2. Click the “Manage” link next to your .gov domain, then click on “Domain managers” to see who has access to your domain. 
+    3. If any of these users should not have access to your domain, let us know in a reply to this email.
+
+After verifying who has access to your domain{% if domains|length > 1 %}s{% endif %}, we also suggest reviewing your contact information and organization mailing address to ensure those are up to date. 
+
+
+DOMAIN EXPIRATION DATES EXTENDED BY ONE YEAR
+
+Expiration dates for .gov domains in good standing have been extended for one year. Expiration dates won't be shown in the new registrar yet. 
 
-YOU NEED A LOGIN.GOV ACCOUNT
-You’ll need a Login.gov account to manage your .gov domain{% if domains|length > 1 %}s{% endif %}. Login.gov provides a simple and secure process for signing into many government services with one account. If you don’t already have one, follow these steps to create your Login.gov account <https://login.gov/help/get-started/create-your-account/>. 
 
-DOMAIN MANAGEMENT
-As a .gov domain manager you can add or update information about your domain{% if domains|length > 1 %}s{% endif %}. You’ll also serve as a contact for your .gov domain{% if domains|length > 1 %}s{% endif %}. Please keep your contact information updated. Learn more about domain management <https://get.gov/help/>.
-{% if domains|length > 1 %}
-DOMAINS
-{% for domain in domains %} {{ domain }}
-{% endfor %}{% else %}
-{% endif %}
 SOMETHING WRONG?
-If you’re not affiliated with {{ domain }} or think you received this message in error, contact the .gov team <https://get.gov/help/#contact-us>. 
+
+If you think you received this message in error or have a question, let us know in a reply to this email. 
 
 
 THANK YOU
@@ -24,6 +45,9 @@ THANK YOU
 ----------------------------------------------------------------
 
 The .gov team
-Contact us: <https://get.gov/contact/>
-Visit <https://get.gov>
+
+.Gov blog <https://get.gov/updates/> 
+Domain management <https://manage.get.gov>
+Contact us <https://get.gov/help/#contact-us> 
+Get.gov <https://get.gov>
 {% endautoescape %}
diff --git a/src/registrar/templates/emails/transition_domain_invitation_subject.txt b/src/registrar/templates/emails/transition_domain_invitation_subject.txt
index 9302a748e..526c7714b 100644
--- a/src/registrar/templates/emails/transition_domain_invitation_subject.txt
+++ b/src/registrar/templates/emails/transition_domain_invitation_subject.txt
@@ -1 +1 @@
-You've been added to a .gov domain
\ No newline at end of file
+(Action required) Manage your .gov domain{% if domains|length > 1 %}s{% endif %} in the new registrar
\ No newline at end of file

From 131d279fbbc4f83f87771a3b005f57772eb01cec Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 07:45:21 -0700
Subject: [PATCH 14/33] Change tooltip color

---
 src/registrar/assets/sass/_theme/_uswds-theme.scss | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/registrar/assets/sass/_theme/_uswds-theme.scss b/src/registrar/assets/sass/_theme/_uswds-theme.scss
index ba076d845..68d5fbb4a 100644
--- a/src/registrar/assets/sass/_theme/_uswds-theme.scss
+++ b/src/registrar/assets/sass/_theme/_uswds-theme.scss
@@ -132,4 +132,10 @@ in the form $setting: value,
   $theme-table-sorted-background-color: "accent-cool-lightest",
   $theme-table-sorted-icon-color: "primary-darker",
   $theme-table-unsorted-icon-color: "primary",
+
+  /*----------------------------
+  # Tooltip Settings
+  -----------------------------*/
+  $theme-tooltip-background-color: "accent-cool-lighter",
+  $theme-tooltip-font-color: "black"
 );

From e7cf834439115b2b9752ab039a0b6b7f6bdbfc2f Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 08:47:32 -0700
Subject: [PATCH 15/33] Add right coloring

---
 src/registrar/assets/sass/_theme/_uswds-theme.scss | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/assets/sass/_theme/_uswds-theme.scss b/src/registrar/assets/sass/_theme/_uswds-theme.scss
index 68d5fbb4a..349285333 100644
--- a/src/registrar/assets/sass/_theme/_uswds-theme.scss
+++ b/src/registrar/assets/sass/_theme/_uswds-theme.scss
@@ -136,6 +136,6 @@ in the form $setting: value,
   /*----------------------------
   # Tooltip Settings
   -----------------------------*/
-  $theme-tooltip-background-color: "accent-cool-lighter",
+  $theme-tooltip-background-color: $theme-color-accent-cool-lightest,
   $theme-tooltip-font-color: "black"
 );

From cbb5ad6217a6cf2ada0a8a8aa14b6954fdb64edc Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 08:57:42 -0700
Subject: [PATCH 16/33] Update _uswds-theme.scss

---
 src/registrar/assets/sass/_theme/_uswds-theme.scss | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/assets/sass/_theme/_uswds-theme.scss b/src/registrar/assets/sass/_theme/_uswds-theme.scss
index 349285333..673f025d4 100644
--- a/src/registrar/assets/sass/_theme/_uswds-theme.scss
+++ b/src/registrar/assets/sass/_theme/_uswds-theme.scss
@@ -136,6 +136,6 @@ in the form $setting: value,
   /*----------------------------
   # Tooltip Settings
   -----------------------------*/
-  $theme-tooltip-background-color: $theme-color-accent-cool-lightest,
+  $theme-tooltip-background-color: "D6E9F2",
   $theme-tooltip-font-color: "black"
 );

From 1543a97dd9a8cd1ddd643d3b935389a851902913 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 09:08:51 -0700
Subject: [PATCH 17/33] Refix coloring - typo

---
 src/registrar/assets/sass/_theme/_uswds-theme.scss | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/assets/sass/_theme/_uswds-theme.scss b/src/registrar/assets/sass/_theme/_uswds-theme.scss
index 673f025d4..0cdf6675e 100644
--- a/src/registrar/assets/sass/_theme/_uswds-theme.scss
+++ b/src/registrar/assets/sass/_theme/_uswds-theme.scss
@@ -136,6 +136,6 @@ in the form $setting: value,
   /*----------------------------
   # Tooltip Settings
   -----------------------------*/
-  $theme-tooltip-background-color: "D6E9F2",
+  $theme-tooltip-background-color: "accent-cool-lightest",
   $theme-tooltip-font-color: "black"
 );

From 4ec861216942c73ddf1984185c831e878684a910 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 10:46:52 -0700
Subject: [PATCH 18/33] Fix andi and coloring

---
 src/registrar/assets/sass/_theme/_buttons.scss | 3 +++
 src/registrar/templates/home.html              | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/src/registrar/assets/sass/_theme/_buttons.scss b/src/registrar/assets/sass/_theme/_buttons.scss
index 2f85bc542..02089ec6d 100644
--- a/src/registrar/assets/sass/_theme/_buttons.scss
+++ b/src/registrar/assets/sass/_theme/_buttons.scss
@@ -28,17 +28,20 @@ a.usa-button {
 
 a.usa-button.disabled-link {
   background-color: #ccc !important;
+  color: #454545 !important
 }
 
 a.usa-button.disabled-link:hover {
   background-color: #ccc !important;
   cursor: not-allowed !important;
+  color: #454545 !important
 }
 
 a.usa-button.disabled-link:focus {
   background-color: #ccc !important;
   cursor: not-allowed !important;
   outline: none !important;
+  color: #454545 !important
 }
 
 a.usa-button:not(.usa-button--unstyled, .usa-button--outline) {
diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index f23fd9a6d..93da259a7 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -18,6 +18,9 @@
     class="usa-button usa-tooltip disabled-link"
     data-position="right"
     title="Coming in 2024"
+    aria-disabled="true"
+    aria-label="Coming in 2024" 
+    data-tooltip="true"
     >
       Start a new domain request
     </a>

From 1147559d6de906abc2d23dc81914ba4585650208 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 10:51:40 -0700
Subject: [PATCH 19/33] Fix VO issue

---
 src/registrar/templates/home.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index 93da259a7..67960e8a2 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -13,13 +13,12 @@
   <h1>Manage your domains</h2>
 
   <p class="margin-top-4">
-    {% if is_production %}
+    {% if not is_production %}
     <a href="javascript:void(0)" 
     class="usa-button usa-tooltip disabled-link"
     data-position="right"
     title="Coming in 2024"
     aria-disabled="true"
-    aria-label="Coming in 2024" 
     data-tooltip="true"
     >
       Start a new domain request

From 3287640fd1d1671d7909aecbe2050e2c937d7355 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 10:53:40 -0700
Subject: [PATCH 20/33] Update home.html

---
 src/registrar/templates/home.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/templates/home.html b/src/registrar/templates/home.html
index 67960e8a2..1605499e2 100644
--- a/src/registrar/templates/home.html
+++ b/src/registrar/templates/home.html
@@ -13,7 +13,7 @@
   <h1>Manage your domains</h2>
 
   <p class="margin-top-4">
-    {% if not is_production %}
+    {% if is_production %}
     <a href="javascript:void(0)" 
     class="usa-button usa-tooltip disabled-link"
     data-position="right"

From b77a546a064ef29be07b7e99a9e18ab720ad8f00 Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Tue, 7 Nov 2023 12:12:33 -0800
Subject: [PATCH 21/33] updated domain invitation txt with feedback

---
 .../templates/emails/transition_domain_invitation.txt        | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/src/registrar/templates/emails/transition_domain_invitation.txt b/src/registrar/templates/emails/transition_domain_invitation.txt
index e97aa322d..81790c138 100644
--- a/src/registrar/templates/emails/transition_domain_invitation.txt
+++ b/src/registrar/templates/emails/transition_domain_invitation.txt
@@ -15,12 +15,13 @@ You can’t use your old credentials to access the new registrar. Access is now
 
 When creating an account, you’ll need to provide the same email address you used to log in to the old registrar. That will ensure your domains are linked to your Login.gov account. 
 
-If you need help finding the email you used in the past, let us know in a reply to this email.
+If you need help finding the email address you used in the past, let us know in a reply to this email.
 
 
 CHECK YOUR .GOV DOMAIN CONTACTS
 
-This is a good time to check who has access to your .gov domain{% if domains|length > 1 %}s{% endif %}. The admin, technical, and billing contacts listed for your domain{% if domains|length > 1 %}s{% endif %} in our old system also received this email. However, in our new registrar, these contacts are all considered “domain managers.” We no longer have the admin, technical, and billing roles, and you aren’t limited to three domain managers like in the old system. 
+This is a good time to check who has access to your .gov domain{% if domains|length > 1 %}s{% endif %}. The admin, technical, and billing contacts listed for your domain{% if domains|length > 1 %}s{% endif %} in our old system also received this email. In our new registrar, these contacts are all considered “domain managers"
+
     1. Once you have your Login.gov account, sign in to the new registrar at <https://manage.get.gov>
     2. Click the “Manage” link next to your .gov domain, then click on “Domain managers” to see who has access to your domain. 
     3. If any of these users should not have access to your domain, let us know in a reply to this email.

From fbb5630f9e2a972b20c2dd2dce204c81e2f1cc22 Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Tue, 7 Nov 2023 13:08:13 -0800
Subject: [PATCH 22/33] added period and removed contact us

---
 .../templates/emails/transition_domain_invitation.txt          | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/registrar/templates/emails/transition_domain_invitation.txt b/src/registrar/templates/emails/transition_domain_invitation.txt
index 81790c138..2c01c4704 100644
--- a/src/registrar/templates/emails/transition_domain_invitation.txt
+++ b/src/registrar/templates/emails/transition_domain_invitation.txt
@@ -20,7 +20,7 @@ If you need help finding the email address you used in the past, let us know in
 
 CHECK YOUR .GOV DOMAIN CONTACTS
 
-This is a good time to check who has access to your .gov domain{% if domains|length > 1 %}s{% endif %}. The admin, technical, and billing contacts listed for your domain{% if domains|length > 1 %}s{% endif %} in our old system also received this email. In our new registrar, these contacts are all considered “domain managers"
+This is a good time to check who has access to your .gov domain{% if domains|length > 1 %}s{% endif %}. The admin, technical, and billing contacts listed for your domain{% if domains|length > 1 %}s{% endif %} in our old system also received this email. In our new registrar, these contacts are all considered “domain managers."
 
     1. Once you have your Login.gov account, sign in to the new registrar at <https://manage.get.gov>
     2. Click the “Manage” link next to your .gov domain, then click on “Domain managers” to see who has access to your domain. 
@@ -49,6 +49,5 @@ The .gov team
 
 .Gov blog <https://get.gov/updates/> 
 Domain management <https://manage.get.gov>
-Contact us <https://get.gov/help/#contact-us> 
 Get.gov <https://get.gov>
 {% endautoescape %}

From 567fcbc78db90fd013471b3a253604e6fd844332 Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 14:45:16 -0700
Subject: [PATCH 23/33] Update .gitignore

---
 .gitignore | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/.gitignore b/.gitignore
index a4df194fa..ef9f654c0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -171,3 +171,14 @@ node_modules
 
 # Compliance/trestle related
 docs/compliance/.trestle/cache
+src/migrationdata/20231009.agency.adhoc.dotgov.txt
+src/migrationdata/20231009.authority.adhoc.dotgov.txt
+src/migrationdata/20231009.domainadditionaldatalink.adhoc.dotgov.txt
+src/migrationdata/20231009.domaindocumentdatalink.adhoc.dotgov.txt
+src/migrationdata/20231009.domaintypes.adhoc.dotgov.txt
+src/migrationdata/20231009.organization.adhoc.dotgov.txt
+src/migrationdata/escrow_contacts.daily.dotgov.GOV.txt
+src/migrationdata/escrow_domain_contacts.daily.dotgov.GOV.txt
+src/migrationdata/escrow_domain_statuses.daily.dotgov.GOV.txt
+src/migrationdata/escrow_domains.daily.dotgov.GOV.txt
+src/migrationdata/migrationFilepaths.json

From a06cffa188984e16121358dd5e57d6e033b8ec1a Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Tue, 7 Nov 2023 15:08:47 -0700
Subject: [PATCH 24/33] Revert "Update .gitignore"

This reverts commit 567fcbc78db90fd013471b3a253604e6fd844332.
---
 .gitignore | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/.gitignore b/.gitignore
index ef9f654c0..a4df194fa 100644
--- a/.gitignore
+++ b/.gitignore
@@ -171,14 +171,3 @@ node_modules
 
 # Compliance/trestle related
 docs/compliance/.trestle/cache
-src/migrationdata/20231009.agency.adhoc.dotgov.txt
-src/migrationdata/20231009.authority.adhoc.dotgov.txt
-src/migrationdata/20231009.domainadditionaldatalink.adhoc.dotgov.txt
-src/migrationdata/20231009.domaindocumentdatalink.adhoc.dotgov.txt
-src/migrationdata/20231009.domaintypes.adhoc.dotgov.txt
-src/migrationdata/20231009.organization.adhoc.dotgov.txt
-src/migrationdata/escrow_contacts.daily.dotgov.GOV.txt
-src/migrationdata/escrow_domain_contacts.daily.dotgov.GOV.txt
-src/migrationdata/escrow_domain_statuses.daily.dotgov.GOV.txt
-src/migrationdata/escrow_domains.daily.dotgov.GOV.txt
-src/migrationdata/migrationFilepaths.json

From 8108ba8b8f3b1b31670314419f9cd9c35b5f78fe Mon Sep 17 00:00:00 2001
From: Rebecca Hsieh <rebecca.hsieh@truss.works>
Date: Tue, 7 Nov 2023 15:35:45 -0800
Subject: [PATCH 25/33] Adding cors regex

---
 src/registrar/config/settings.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/config/settings.py b/src/registrar/config/settings.py
index 896691efb..90ca1c421 100644
--- a/src/registrar/config/settings.py
+++ b/src/registrar/config/settings.py
@@ -300,7 +300,7 @@ CSP_FORM_ACTION = allowed_sources
 # Sets clients that allow access control to manage.get.gov
 # TODO: remove :8080 to see if we can have all localhost access
 CORS_ALLOWED_ORIGINS = ["http://localhost:8080", "https://beta.get.gov"]
-
+CORS_ALLOWED_ORIGIN_REGEXES = [r"https://\w+\.sites\.pages\.cloud\.gov/"]
 
 # Content-Length header is set by django.middleware.common.CommonMiddleware
 

From b67bdc85cab74d1cff7c941166f1a27e515ec2f3 Mon Sep 17 00:00:00 2001
From: Rebecca Hsieh <rebecca.hsieh@truss.works>
Date: Tue, 7 Nov 2023 15:47:40 -0800
Subject: [PATCH 26/33] Fix regex

---
 src/registrar/config/settings.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/config/settings.py b/src/registrar/config/settings.py
index 90ca1c421..2a0a205ea 100644
--- a/src/registrar/config/settings.py
+++ b/src/registrar/config/settings.py
@@ -300,7 +300,7 @@ CSP_FORM_ACTION = allowed_sources
 # Sets clients that allow access control to manage.get.gov
 # TODO: remove :8080 to see if we can have all localhost access
 CORS_ALLOWED_ORIGINS = ["http://localhost:8080", "https://beta.get.gov"]
-CORS_ALLOWED_ORIGIN_REGEXES = [r"https://\w+\.sites\.pages\.cloud\.gov/"]
+CORS_ALLOWED_ORIGIN_REGEXES = [r"https:\/\/[\w-]+\.sites\.pages\.cloud\.gov"]
 
 # Content-Length header is set by django.middleware.common.CommonMiddleware
 

From 011d979947e04545b71e95b796e787d564cec6b1 Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Tue, 7 Nov 2023 16:44:52 -0800
Subject: [PATCH 27/33] added missing period

---
 .../templates/emails/transition_domain_invitation.txt        | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/src/registrar/templates/emails/transition_domain_invitation.txt b/src/registrar/templates/emails/transition_domain_invitation.txt
index 2c01c4704..e6e3eabc3 100644
--- a/src/registrar/templates/emails/transition_domain_invitation.txt
+++ b/src/registrar/templates/emails/transition_domain_invitation.txt
@@ -17,12 +17,11 @@ When creating an account, you’ll need to provide the same email address you us
 
 If you need help finding the email address you used in the past, let us know in a reply to this email.
 
-
 CHECK YOUR .GOV DOMAIN CONTACTS
 
-This is a good time to check who has access to your .gov domain{% if domains|length > 1 %}s{% endif %}. The admin, technical, and billing contacts listed for your domain{% if domains|length > 1 %}s{% endif %} in our old system also received this email. In our new registrar, these contacts are all considered “domain managers."
+This is a good time to check who has access to your .gov domain{% if domains|length > 1 %}s{% endif %}. The admin, technical, and billing contacts listed for your domain{% if domains|length > 1 %}s{% endif %} in our old system also received this email. In our new registrar, these contacts are all considered “domain managers.” We no longer have the admin, technical, and billing roles, and you aren’t limited to three domain managers like in the old system. 
 
-    1. Once you have your Login.gov account, sign in to the new registrar at <https://manage.get.gov>
+    1. Once you have your Login.gov account, sign in to the new registrar at <https://manage.get.gov>.
     2. Click the “Manage” link next to your .gov domain, then click on “Domain managers” to see who has access to your domain. 
     3. If any of these users should not have access to your domain, let us know in a reply to this email.
 

From fa65ba78c6bffd4ee3eb2c6ac9e8cadbe041e523 Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Tue, 7 Nov 2023 21:10:00 -0800
Subject: [PATCH 28/33] updated with review feedback

---
 docs/product/product_strategy.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/docs/product/product_strategy.md b/docs/product/product_strategy.md
index 5ab9b89f8..3caae2634 100644
--- a/docs/product/product_strategy.md
+++ b/docs/product/product_strategy.md
@@ -35,14 +35,15 @@ Bugs on production software need to be documented quickly and triaged to determi
 ### Steps for Triaging
 
 1. When a bug is found, whether by a developer/designer or from feedback from an end user, a ticket should be made immediately. The actual maker of the ticket can be a member of the product team as needed.
-2. This bug ticket immediately gets a priority added Critical/High/Medium/Low, with Critcal requiring the product owner's request.
-3. Anything marked as `critical` should be refined immediately and engineering should be notified via Slack that a Critical ticket has been created (if not already notified)
-4. All items not marked as `critical` by the product owner, can wait until refinement to be refined and may have their prioirty level changed during that meeting.
+2. This bug ticket immediately gets a priority added Critical/High/Medium/Low, with Critical requiring the product owner's consent.
+3. Anything marked as `critical` should be refined immediately and engineering should be notified in our Slack dev channel that a Critical ticket has been created (if not already notified)
+4. All items not marked as `critical` by the product owner can wait until refinement to be refined and may have their prioirty level changed during that meeting.
 
 ### Steps for dealing with Critical Bugs
 
 1. Once the critical bug ticket is refined and the bug is clear, an engineer should be assigned to work on it. (No ticket, no work)
 2. At the same point, two other engineers should be assigned to review the PR once it's made. One of the reviewing engineers can be subsititued for a designer if this is a design/content/other user facing bug fix.
-3. In the case where the engineering lead is not responsive/ unavailable to assign the ticket immediatley, other engineers should see the public slack message and volunteer as needed. The product team will be backup to make sure someone is assigned or volunteers for the ticket/PR review ASAP.
-4. Once done the developer, now needs to make a PR as usual but should tag the assigned PR reviewers in a public slack message stating that the PR is now waiting on their review. These reviewers should drop other tasks in order to review this promptly.
+3. In the case where the engineering lead is is unresponsive or unavailable to assign the ticket immediately, the product team will make sure an engineer volunteers or is assigned to the ticket/PR review ASAP.
+
+4. Once done, the developer must make a PR and should tag the assigned PR reviewers in our Slack dev channel stating that the PR is now waiting on their review. These reviewers should drop other tasks in order to review this promptly.
 5. See the Making bug fixes on stable during production readme for how to push changes to stable once the PR is approved

From 9f9048409e9ead073287ad9015e59ee8661c919c Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Tue, 7 Nov 2023 21:13:44 -0800
Subject: [PATCH 29/33] updated with link to other readme

---
 docs/product/product_strategy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/product/product_strategy.md b/docs/product/product_strategy.md
index 3caae2634..3c91afc2d 100644
--- a/docs/product/product_strategy.md
+++ b/docs/product/product_strategy.md
@@ -46,4 +46,4 @@ Bugs on production software need to be documented quickly and triaged to determi
 3. In the case where the engineering lead is is unresponsive or unavailable to assign the ticket immediately, the product team will make sure an engineer volunteers or is assigned to the ticket/PR review ASAP.
 
 4. Once done, the developer must make a PR and should tag the assigned PR reviewers in our Slack dev channel stating that the PR is now waiting on their review. These reviewers should drop other tasks in order to review this promptly.
-5. See the Making bug fixes on stable during production readme for how to push changes to stable once the PR is approved
+5. See the [Making bug fixes on stable during production readme](../operations/README.md) for how to push changes to stable once the PR is approved

From 0c045429fdb0970e8d5416a5905e26c6a9049821 Mon Sep 17 00:00:00 2001
From: Alysia Broddrick <abroddrick@truss.works>
Date: Wed, 8 Nov 2023 07:18:45 -0800
Subject: [PATCH 30/33] moved the bug triage section to operations/readme

---
 docs/operations/README.md        | 24 ++++++++++++++++++++++++
 docs/product/product_strategy.md | 25 -------------------------
 2 files changed, 24 insertions(+), 25 deletions(-)

diff --git a/docs/operations/README.md b/docs/operations/README.md
index 047e335f1..f18d24115 100644
--- a/docs/operations/README.md
+++ b/docs/operations/README.md
@@ -174,3 +174,27 @@ it with the latest model schema. Once launched, this should never be used on
 the `stable` environment, but during development, it may be useful on the
 various sandbox environments. After launch, some schema changes may take the
 involvement of a skilled DBA to fix problems like this.
+
+# Bug triage
+
+Bugs on production software need to be documented quickly and triaged to determine if fixes need to be made outside of the normal release cadence. Triage levels will be Critical, High, Medium, and Low to indicate the level of priority for fix, not neccessarily the level of severity. See below for more details
+
+**Critical**- should only be determined by the product owner and means the fix for this critical bug needs to have a quick fix for it created ASAP. This is the only case where a bug fix can be added outside of the normal release cycle and directly onto the stable release.
+**High**- Can be determined by product owner or other team member, and indicates this bug is critical enough to warrant being added into the current sprint.
+**Medium**- Should be added to a sprint coming up but is not blocking users, or enough users to warrant rushing it into a sprint
+**Low**- A minor bug, that could even wait until after the next big launch date to be implemented.
+
+## Steps for Triaging
+
+1. When a bug is found, whether by a developer/designer or from feedback from an end user, a ticket should be made immediately. The actual maker of the ticket can be a member of the product team as needed.
+2. This bug ticket immediately gets a priority added Critical/High/Medium/Low, with Critical requiring the product owner's consent.
+3. Anything marked as `critical` should be refined immediately and engineering should be notified in our Slack dev channel that a Critical ticket has been created (if not already notified)
+4. All items not marked as `critical` by the product owner can wait until refinement to be refined and may have their prioirty level changed during that meeting.
+
+## Steps for dealing with Critical Bugs
+
+1. Once the critical bug ticket is refined and the bug is clear, an engineer should be assigned to work on it. (No ticket, no work)
+2. At the same point, two other engineers should be assigned to review the PR once it's made. One of the reviewing engineers can be subsititued for a designer if this is a design/content/other user facing bug fix.
+3. In the case where the engineering lead is is unresponsive or unavailable to assign the ticket immediately, the product team will make sure an engineer volunteers or is assigned to the ticket/PR review ASAP.
+4. Once done, the developer must make a PR and should tag the assigned PR reviewers in our Slack dev channel stating that the PR is now waiting on their review. These reviewers should drop other tasks in order to review this promptly.
+5. See the the section above on [Making bug fixes on stable](#making-bug-fixes-on-stable-during-production) for how to push changes to stable once the PR is approved
diff --git a/docs/product/product_strategy.md b/docs/product/product_strategy.md
index 3c91afc2d..1a17727d1 100644
--- a/docs/product/product_strategy.md
+++ b/docs/product/product_strategy.md
@@ -22,28 +22,3 @@ CISA lacks a scalable, efficient, and secure method of managing the .gov TLD pro
 | **Data:** The program maintains authoritative contacts at, metadata about, and hostname information for all registered .gov domains, and is able to track that .gov domains are actually used | - Time-to-generate internal reports decreases <br /> - Results of periodic data quality audit show improvements month-over-month                                                                              |
 | **User satisfaction:** Getting a .gov domain is as easy and intuitive as possible                                                                                                             | - Completion rate of form improves <br /> - Time from domain request to approval decreases <br /> - Number of domains requiring analyst data changes decreases                                                        |
 | **Program reputation and experience:** The .gov program is viewed as trustworthy and responsive                                                                                               | - Response time for inquiries decreases <br /> - Resolution time decreases <br /> - Rate of repeat issues for tickets decreases <br /> - Number of SLTT organizations in Community of Practice increases                                      |
-
-## Bug triage
-
-Bugs on production software need to be documented quickly and triaged to determine if fixes need to be made outside of the normal release cadence. Triage levels will be Critical, High, Medium, and Low to indicate the level of priority for fix, not neccessarily the level of severity. See below for more details
-
-**Critical**- should only be determined by the product owner and means the fix for this critical bug needs to have a quick fix for it created ASAP. This is the only case where a bug fix can be added outside of the normal release cycle and directly onto the stable release.
-**High**- Can be determined by product owner or other team member, and indicates this bug is critical enough to warrant being added into the current sprint.
-**Medium**- Should be added to a sprint coming up but is not blocking users, or enough users to warrant rushing it into a sprint
-**Low**- A minor bug, that could even wait until after the next big launch date to be implemented.
-
-### Steps for Triaging
-
-1. When a bug is found, whether by a developer/designer or from feedback from an end user, a ticket should be made immediately. The actual maker of the ticket can be a member of the product team as needed.
-2. This bug ticket immediately gets a priority added Critical/High/Medium/Low, with Critical requiring the product owner's consent.
-3. Anything marked as `critical` should be refined immediately and engineering should be notified in our Slack dev channel that a Critical ticket has been created (if not already notified)
-4. All items not marked as `critical` by the product owner can wait until refinement to be refined and may have their prioirty level changed during that meeting.
-
-### Steps for dealing with Critical Bugs
-
-1. Once the critical bug ticket is refined and the bug is clear, an engineer should be assigned to work on it. (No ticket, no work)
-2. At the same point, two other engineers should be assigned to review the PR once it's made. One of the reviewing engineers can be subsititued for a designer if this is a design/content/other user facing bug fix.
-3. In the case where the engineering lead is is unresponsive or unavailable to assign the ticket immediately, the product team will make sure an engineer volunteers or is assigned to the ticket/PR review ASAP.
-
-4. Once done, the developer must make a PR and should tag the assigned PR reviewers in our Slack dev channel stating that the PR is now waiting on their review. These reviewers should drop other tasks in order to review this promptly.
-5. See the [Making bug fixes on stable during production readme](../operations/README.md) for how to push changes to stable once the PR is approved

From 8cf1296e77d5c59238cf3721a8ccf8dd85c20f3c Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Wed, 8 Nov 2023 08:44:48 -0700
Subject: [PATCH 31/33] Update manifest-za.yaml

---
 ops/manifests/manifest-za.yaml | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/ops/manifests/manifest-za.yaml b/ops/manifests/manifest-za.yaml
index 774ed57ec..23b6179ec 100644
--- a/ops/manifests/manifest-za.yaml
+++ b/ops/manifests/manifest-za.yaml
@@ -23,9 +23,6 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
-    # NOTE: This needs to go in manifest-staging
-    # This is here for PR purposes only!
-    IS_PRODUCTION: True
   routes:
     - route: getgov-za.app.cloud.gov
   services:

From 802f8092a7c98f7b527390c905e9c9c415076d83 Mon Sep 17 00:00:00 2001
From: Rebecca Hsieh <rebecca.hsieh@truss.works>
Date: Wed, 8 Nov 2023 08:43:58 -0800
Subject: [PATCH 32/33] Test removal of backslashes

---
 src/registrar/config/settings.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/registrar/config/settings.py b/src/registrar/config/settings.py
index 2a0a205ea..37c661e16 100644
--- a/src/registrar/config/settings.py
+++ b/src/registrar/config/settings.py
@@ -300,7 +300,7 @@ CSP_FORM_ACTION = allowed_sources
 # Sets clients that allow access control to manage.get.gov
 # TODO: remove :8080 to see if we can have all localhost access
 CORS_ALLOWED_ORIGINS = ["http://localhost:8080", "https://beta.get.gov"]
-CORS_ALLOWED_ORIGIN_REGEXES = [r"https:\/\/[\w-]+\.sites\.pages\.cloud\.gov"]
+CORS_ALLOWED_ORIGIN_REGEXES = [r"https://[\w-]+\.sites\.pages\.cloud\.gov"]
 
 # Content-Length header is set by django.middleware.common.CommonMiddleware
 

From 6e9eb98970ad9025bd3f4d25559b0096d1d5d36d Mon Sep 17 00:00:00 2001
From: zandercymatics <141044360+zandercymatics@users.noreply.github.com>
Date: Wed, 8 Nov 2023 14:23:41 -0700
Subject: [PATCH 33/33] Add correct flag to each

---
 ops/manifests/manifest-ab.yaml             | 2 ++
 ops/manifests/manifest-bl.yaml             | 2 ++
 ops/manifests/manifest-dk.yaml             | 2 ++
 ops/manifests/manifest-es.yaml             | 2 ++
 ops/manifests/manifest-gd.yaml             | 2 ++
 ops/manifests/manifest-ko.yaml             | 2 ++
 ops/manifests/manifest-nl.yaml             | 2 ++
 ops/manifests/manifest-rb.yaml             | 2 ++
 ops/manifests/manifest-rh.yaml             | 2 ++
 ops/manifests/manifest-rjm.yaml            | 2 ++
 ops/manifests/manifest-staging.yaml        | 2 ++
 ops/manifests/manifest-za.yaml             | 2 ++
 ops/scripts/manifest-sandbox-template.yaml | 2 ++
 src/docker-compose.yml                     | 2 ++
 14 files changed, 28 insertions(+)

diff --git a/ops/manifests/manifest-ab.yaml b/ops/manifests/manifest-ab.yaml
index f3dd170e6..38109bdcb 100644
--- a/ops/manifests/manifest-ab.yaml
+++ b/ops/manifests/manifest-ab.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-ab.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-bl.yaml b/ops/manifests/manifest-bl.yaml
index 3a494aa25..59529278b 100644
--- a/ops/manifests/manifest-bl.yaml
+++ b/ops/manifests/manifest-bl.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-bl.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-dk.yaml b/ops/manifests/manifest-dk.yaml
index 61036b739..256beeda2 100644
--- a/ops/manifests/manifest-dk.yaml
+++ b/ops/manifests/manifest-dk.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-dk.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-es.yaml b/ops/manifests/manifest-es.yaml
index c4847553f..47c78ce1b 100644
--- a/ops/manifests/manifest-es.yaml
+++ b/ops/manifests/manifest-es.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-es.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-gd.yaml b/ops/manifests/manifest-gd.yaml
index bb07e78ec..0c4b2535f 100644
--- a/ops/manifests/manifest-gd.yaml
+++ b/ops/manifests/manifest-gd.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-gd.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-ko.yaml b/ops/manifests/manifest-ko.yaml
index 7681d9527..cc6a09337 100644
--- a/ops/manifests/manifest-ko.yaml
+++ b/ops/manifests/manifest-ko.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-ko.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-nl.yaml b/ops/manifests/manifest-nl.yaml
index 6c848db78..ca6fb4693 100644
--- a/ops/manifests/manifest-nl.yaml
+++ b/ops/manifests/manifest-nl.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-nl.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-rb.yaml b/ops/manifests/manifest-rb.yaml
index c51230eb4..62f243513 100644
--- a/ops/manifests/manifest-rb.yaml
+++ b/ops/manifests/manifest-rb.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-rb.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-rh.yaml b/ops/manifests/manifest-rh.yaml
index ac88a8031..4985f3261 100644
--- a/ops/manifests/manifest-rh.yaml
+++ b/ops/manifests/manifest-rh.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-rh.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-rjm.yaml b/ops/manifests/manifest-rjm.yaml
index 45a12f363..7d72e7835 100644
--- a/ops/manifests/manifest-rjm.yaml
+++ b/ops/manifests/manifest-rjm.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-rjm.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-staging.yaml b/ops/manifests/manifest-staging.yaml
index a1d09a555..b616973ac 100644
--- a/ops/manifests/manifest-staging.yaml
+++ b/ops/manifests/manifest-staging.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-staging.app.cloud.gov
   services:
diff --git a/ops/manifests/manifest-za.yaml b/ops/manifests/manifest-za.yaml
index 23b6179ec..1b84a74a1 100644
--- a/ops/manifests/manifest-za.yaml
+++ b/ops/manifests/manifest-za.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-za.app.cloud.gov
   services:
diff --git a/ops/scripts/manifest-sandbox-template.yaml b/ops/scripts/manifest-sandbox-template.yaml
index 3acbb910c..8cdb8d71b 100644
--- a/ops/scripts/manifest-sandbox-template.yaml
+++ b/ops/scripts/manifest-sandbox-template.yaml
@@ -23,6 +23,8 @@ applications:
     DJANGO_LOG_LEVEL: INFO
     # default public site location
     GETGOV_PUBLIC_SITE_URL: https://beta.get.gov
+    # Flag to disable/enable features in prod environments
+    IS_PRODUCTION: False
   routes:
     - route: getgov-ENVIRONMENT.app.cloud.gov
   services:
diff --git a/src/docker-compose.yml b/src/docker-compose.yml
index 786f4c24b..a45ea2a51 100644
--- a/src/docker-compose.yml
+++ b/src/docker-compose.yml
@@ -25,6 +25,8 @@ services:
       - DJANGO_SECRET_KEY=really-long-random-string-BNPecI7+s8jMahQcGHZ3XQ5yUfRrSibdapVLIz0UemdktVPofDKcoy
       # Run Django in debug mode on local
       - DJANGO_DEBUG=True
+      # Run Django without production flags
+      - IS_PRODUCTION=False
       # Tell Django where it is being hosted
       - DJANGO_BASE_URL=http://localhost:8080
       # Public site URL link