From fdabbfeae4d4a40b7f4b7da38249822a0f587164 Mon Sep 17 00:00:00 2001
From: Emily Rockman <ebuschang@gmail.com>
Date: Mon, 22 Jan 2024 14:33:23 -0600
Subject: [PATCH] add slash command template (#32)

Co-authored-by: Michelle Ark <MichelleArk@users.noreply.github.com>
---
 .../ISSUE_TEMPLATE/implementation-ticket.yml  | 10 ++++++++
 .../ISSUE_TEMPLATE/slash-command-template.md  | 23 +++++++++++++++++++
 2 files changed, 33 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/slash-command-template.md

diff --git a/.github/ISSUE_TEMPLATE/implementation-ticket.yml b/.github/ISSUE_TEMPLATE/implementation-ticket.yml
index 9bc709e9..18b24046 100644
--- a/.github/ISSUE_TEMPLATE/implementation-ticket.yml
+++ b/.github/ISSUE_TEMPLATE/implementation-ticket.yml
@@ -30,6 +30,16 @@ body:
         What is the definition of done for this ticket? Include any relevant edge cases and/or test cases
     validations:
       required: true
+  - type: textarea
+    attributes:
+      label: Suggested Tests
+      description: |
+        Provide scenarios to test.  Link to existing similar tests if appropriate.
+      placeholder: |
+         1. Test with no version specified in the schema file and use selection logic on a versioned model for a specific version.  Expect pass.
+         2. Test with a version specified in the schema file that is no valid.  Expect ParsingError.
+    validations:
+      required: true
   - type: textarea
     attributes:
       label: Impact to Other Teams
diff --git a/.github/ISSUE_TEMPLATE/slash-command-template.md b/.github/ISSUE_TEMPLATE/slash-command-template.md
new file mode 100644
index 00000000..059b2498
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/slash-command-template.md
@@ -0,0 +1,23 @@
+## Short description
+
+<!-- Describe the scope of the ticket, a high-level implementation approach and any tradeoffs to consider -->
+
+## Acceptance criteria
+
+<!-- What is the definition of done for this ticket? Include any relevant edge cases and/or test cases -->
+
+## Suggested Tests
+
+<!-- Provide scenarios to test. Link to existing similar tests if appropriate. -->
+
+## Impact to Other Teams
+
+<!-- Will this change impact other teams?  Include details of the kinds of changes required (new tests, code changes, related tickets) and _add the relevant `Impact:[team]` label_. -->
+
+## Will backports be required?
+
+<!-- Will this change need to be backported to previous versions?  Add details, possible blockers to backporting and _add the relevant backport labels `backport 1.x.latest`_ -->
+
+## Context
+
+<!-- Provide the "why", motivation, and alternative approaches considered -- linking to previous refinement issues, spikes, docs as appropriate -->