Value Statement

The policy template details page has the card on the left of the page with details and the YAML editor on the right side. This makes the YAML editor a bit too small so let's copy what the search results show and have one tab for "Details" and one for "YAML". The "Details" page will contain the current details and related resources table.

Search examples:

Definition of Done for Engineering Story Owner (Checklist)

• Two tabs are added to the policy template details page
  • "Details" will contain the current details but the card/table will take up the whole width. Below it will contain the "Related resources" table as it exists today.
  • "YAML" will contain a full width YAML editor.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.