Merge branch 'main' into dependabot/composer/phpstan/phpstan-1.10.65

.github/ISSUE_TEMPLATE/__cms-task.md

@@ -22,11 +22,3 @@ assignees: ''
 - [ ] Testable_Outcome_Z
 - [ ] Requires design review
 - [ ] Requires accessibility review
-
-## Team
-Please check the team(s) that will do this work.
-
-- [ ] CMS Team
-- [ ] Public Websites
-- [ ] Facilities
-- [ ] Accelerated Publishing

.github/ISSUE_TEMPLATE/_cms-epic.md

@@ -1,6 +1,6 @@
 ---
 name: Epic
-about: A epic for the CMS team.
+about: Epic template
 title: "<Insert summary of epic>"
 labels: Epic, Needs refining
 assignees: ''
@@ -77,20 +77,3 @@ Editor-centered
 
 ## Runbook
 <optional>
-
-## Labels
-(You can delete this section once it's complete)
-- [x] Issue type (red) (defaults to "Epic")
-- [ ] CMS subsystem (green)
-- [ ] CMS practice area (blue)
-- [x] CMS workstream (orange)
-- [ ] CMS-supported product (black)
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
-- [ ] `Accelerated Publishing`

.github/ISSUE_TEMPLATE/change-management-epic.md

@@ -51,12 +51,3 @@ If existing videos, list URLs:
 
 ## Acceptance Criteria
 - [ ] All tickets have been created and assigned per [Change Management Runbook](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/facilities/change-management)
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
-- [ ] `Accelerated Publishing`

.github/ISSUE_TEMPLATE/cms-collaboration-cycle-request.yml

@@ -3,8 +3,6 @@ name: "CMS Collaboration Cycle Request"
 description: Use this template to begin engaging with the CMS Collaboration Cycle.
 title: "CMS Collaboration Cycle for [Team Name, Product Name, Feature Name]"
 labels: CMS Team, Needs Analysis, CMS-Collab-Cycle, Epic
-assignees:
-  - BerniXiongA6
 
 
 body:

.github/ISSUE_TEMPLATE/cms-notification-trigger.md

@@ -27,11 +27,3 @@ A trigger is a flag in the CMS that indicates there is an action for a user to c
 **6. Are there any change management implications for this trigger?**
 
 > All requests should be submitted to the Sitewide CMS team for prioritization. Please make sure to notify the Sitewide CMS team after you submit this issue on the #sitewide-cms team slack channel.
-
-### Team
-Please check the team(s) that will do this work.
-
-- [X] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`

.github/ISSUE_TEMPLATE/cms-section-request.md

@@ -2,7 +2,7 @@
 name: CMS section request
 about: Requests a change to the Sections hierarchy
 title: ''
-labels: Content governance
+labels: Content governance, CMS Team
 assignees: ''
 
 ---
@@ -74,14 +74,3 @@ Examples:
 - [ ] New "Resources and support" sections are added under each of the three main Administrations (NCA, VHA, VBA)
 - [ ] All existing Resources and support content is moved to ...
 - [ ] Update X, Y, and Z editors about a change in content access
-
-
-
-
-### Team
-Please check the team(s) that will do this work.
-
-- [X] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`

.github/ISSUE_TEMPLATE/cms-team-member-onboarding.md

@@ -390,4 +390,3 @@ Your discipline lead will assist with onboarding tasks / calls.
 - [ ] Review other Delivery documents in [Google Drive](https://drive.google.com/drive/u/1/folders/1mFC5NCUkeQlGX2S8TIpD1om2V-5B0ikc)
 
 </details>
-

.github/ISSUE_TEMPLATE/content-audit.md

@@ -2,7 +2,7 @@
 name: Content Audit
 about: Submit a request to perform a content audit across VA.gov.
 title: 'Content Audit: <description>'
-labels: Content audit
+labels: Content audit, CMS Team
 assignees: dawnpruitt, EWashb
 
 ---
@@ -21,12 +21,3 @@ Please provide any context for the audit, any related terms or alternate spellin
   - [ ] No
 
 ## 5. When do you need the audit to be completed
-
-
-### Team
-Please check the team(s) that will do this work.
-
-- [x] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`

.github/ISSUE_TEMPLATE/content_model_spec.md

@@ -22,13 +22,4 @@ SO THAT I can implement it in Drupal
 ## Acceptance Criteria
 - [ ] Proposed entities, fields, and field properties are documented using the [content model spec template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/cms/content-model/drupal_content_model_spec_template.xlsx)
 - [ ] Reviewed with engineering & product
-- [ ] Send to CMS Collab Cycle
-
-
-## Team
-Please check the team(s) that will do this work.
-
-- [ ] CMS Team
-- [ ] Public Websites
-- [ ] Facilities
-- [ ] Accelerated Publishing
+- [ ] Send to CMS Collab Cycle

.github/ISSUE_TEMPLATE/cross-team-intake-request.md

@@ -31,13 +31,4 @@ Please provide:
 ## Acceptance Criteria
 - [ ] The Product Manager for the recommended intake team is pinged through Slack about the issue
 - [ ] The Product Manager has discussed with the respective Product Owner to determine prioritization
-- [ ] Any decisions made on prioritization or implementation are communicated back to the originating team
-
-### Team
-Please check the team you project will do this work. If not sure, select "Program".
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
-- [ ] `Accelerated Publishing`
+- [ ] Any decisions made on prioritization or implementation are communicated back to the originating team

.github/ISSUE_TEMPLATE/defect-report.md

@@ -31,20 +31,3 @@ Add any other context about the problem here. Reach out to the Product Managers
  - OS: [e.g. iOS]
  - Browser [e.g. chrome, safari]
  - Version [e.g. 22]
-
-## Labels
-(You can delete this section once it's complete)
-- [x] Issue type (red) (defaults to "Defect")
-- [ ] CMS subsystem (green)
-- [ ] CMS practice area (blue)
-- [x] CMS workstream (orange) (not needed for bug tickets)
-- [ ] CMS-supported product (black)
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
-- [ ] `Accelerated Publishing`

.github/ISSUE_TEMPLATE/devops-task.md

@@ -2,19 +2,10 @@
 name: DevOps task
 about: A task for the CMS DevOps team.
 title: "<Insert summary of task>"
-labels: DevOps, Needs refining
+labels: DevOps, Needs refining, CMS Team
 assignees: ''
 
 ---
 
 ### Tasks:
-- [ ] Task 1...
-
-
-### Team
-Please check the team(s) that will do this work.
-
-- [x] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
+- [ ] Task 1...

.github/ISSUE_TEMPLATE/enhancement.md

@@ -40,12 +40,4 @@ Editor-centered
 - [ ] `Efficient`: Remove distractions and create clear, straightforward paths to get the job done.
 - [ ] `Approachable`: Offer friendly guidance over authoritative instruction.
 - [ ] `Consistent`: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
-- [ ] `Empowering`: Provide clear information to help editors make decisions about their work.
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
+- [ ] `Empowering`: Provide clear information to help editors make decisions about their work.

.github/ISSUE_TEMPLATE/pw-forms-bad-pdf-link-pw.md

@@ -40,11 +40,3 @@ Steps to reproduce the behavior:
 
 ## Acceptance Criteria
 - [ ] Form page loads & form can be downloaded
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [X] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`

.github/ISSUE_TEMPLATE/pw-injected-header-publish.md

@@ -19,12 +19,4 @@ This ticket adds new domain(s) to allowlists that gate the injected header. When
 ## Acceptance Criteria
 - [ ] Devops PRs to add www & non-www domain(s) have merged
 - [ ] Requesting team has signed off that they're ready to publish
-- [ ] On requested domain(s) the global header is injected on page load, with no cookie updates required
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [X] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
+- [ ] On requested domain(s) the global header is injected on page load, with no cookie updates required

.github/ISSUE_TEMPLATE/pw-injected-header.md

@@ -42,11 +42,3 @@ After PW updates allowlists, the requesting team will need to test on Staging by
 ## Acceptance Criteria
 - [ ] On the requested domains, when setting cookie in the console the global header is injected
 - [ ] Let DM know when your changes have deployed to production, so they can notify the requesting team
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [X] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`

.github/ISSUE_TEMPLATE/redirect-request-facility-url.md

@@ -24,12 +24,3 @@ When does this request need to be live:
 | Current URL  |  Redirect Destination or New URL |
 | ---  |  --- |
 | current URL | new URL |
-
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [x] `Facilities`
-- [x] `User support`

.github/ISSUE_TEMPLATE/tier-1-or-2-ongoing-work.md

@@ -19,12 +19,4 @@ Tier 2 expectations here: https://docs.google.com/document/d/15oe0wtGI_MdaScYpjJ
 
 ### Table to help track issues and approximate time spent
 | Date | Issue | Resolution | Time Spent |
-| -- | -- | -- | -- |
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [x] `Facilities`
-- [x] `User support`
+| -- | -- | -- | -- |

.github/ISSUE_TEMPLATE/ux-writing.md

@@ -37,12 +37,4 @@ E.g. *As a user who may be making changes to content, I'd like a message that wa
 - [ ] Validate draft with those responsible for the work
 - [ ] Peer review by a member of the design pod
 - [ ] Finalize edits to text, and mark as ready to implement in the original issue
-- [ ] Document strategy behind language choices that are relevant to [the CMS content style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms/content-style-guide)
-
-### Team
-Please check the team(s) that will do this work.
-
-- [ ] `CMS Team`
-- [ ] `Public Websites`
-- [ ] `Facilities`
-- [ ] `User support`
+- [ ] Document strategy behind language choices that are relevant to [the CMS content style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms/content-style-guide)