Copy streamline templates, but make them AIE (#2234)

aie templates

.github/ISSUE_TEMPLATE/bug-template-aie.md

@@ -0,0 +1,39 @@
+---
+name: AIE Bug Template
+about: Capture bugs with this
+title: ''
+labels: aie
+assignees: ''
+
+---
+
+## Description
+
+_Provide a high-level summary of the bug and what impact it has_
+
+## Steps to reproduce
+
+_List out the steps in detail to reproduce the bug_
+
+1. 
+
+## Expected Result
+
+_Explain how it should function if the bug was fixed. Attach screenshot if applicable_
+
+## Actual result
+
+_Explain what's happening now when the bug is present. Attach screenshot if applicable_
+
+## Priority
+
+_Provide an estimate for level of impact the bug has today by placing an X in the applicable bracket_
+
+#### Priority
+- [ ] **Low priority** _The bug does not have to be fixed immediately. High and medium priority bugs should be addressed first._
+- [ ] **Medium priority** _Typically, medium-priority bugs do not affect customers directly and therefore can be fixed in the normal course of testing and development._
+- [ ] **High priority** _High priority bugs must be addressed immediately. They often affect the app’s functionality and impact customers and their user experience. They must take priority._
+
+## Notes
+
+_Include any additional context or information here that doesn't fit into other parts of the template_

.github/ISSUE_TEMPLATE/qa-ticket-template-aie.md

@@ -0,0 +1,36 @@
+---
+name: AIE QA Ticket Template
+about: Template for eCR Viewer QA efforts
+title: ''
+labels: aie, quality-assurance-testing
+assignees: ''
+
+---
+
+## Action Requested
+As part of our efforts to QA the eCR Viewer please thoroughly test the following eCR in the eCR viewer: [Link to eCR ##: ID]()
+
+## Acceptance Criteria
+- [ ] The eCR has been run through orchestration and the pipeline
+- [ ] The eCR has been viewed in the Viewer and compared side by side to the original XML/HTML file
+- [ ] The eCR is appearing properly in the non-integrated homepage table
+- [ ] All discovered issues are captured and added to our QA spreadsheet [link here]
+
+## Basic process for comparing eCR Viewer output and original eCR
+
+Steps to follow:
+1. Go through the eCR Viewer fields from top to bottom
+2. For every field in the eCR Viewer, do the following:
+      a. Check that you can find the data somewhere in the original HTML or XML
+      b.  Check the content of the fields to see if they are the same or different
+3. Then, looking at the original eCR HTML, do a quick scroll through to see if there is any data or sections present that we aren't showing in the eCR Viewer
+
+Things to look out for:
+- **Do we have only some of the data that you can see in the HTML or XML? Does it seem like it could be important information to users?** 
+  - for ex: if the HTML says "Race: White, European" and ours says "Race: White" --> we will want to note that as a problem that we are missing some data that is available!
+- **Does the formatting of the data look odd/different?** 
+  - for ex: did we get rid of page breaks such that narrative text is an overwhelming wall of text?
+- **Are all addresses and phone numbers available in the HTML or XML available somewhere in our viewer?** 
+  - we want to make sure we aren't missing any potential contact info for facilities that an end user may need to call for follow up
+- **Do you notice anything that seems like a bug with our Viewer?** 
+  - for ex: is there a field showing up with no data in it? is there an edge case with the eCR data you're looking at that we didn't account for?

.github/ISSUE_TEMPLATE/spike-template-aie.md

@@ -0,0 +1,33 @@
+---
+name: AIE Spike Template
+about: Used for exploratory engineering spikes
+title: ''
+labels: aie
+assignees: ''
+
+---
+
+## What needs to be done
+
+_Provide a summary of the task that needs to be completed_
+
+
+## Why it needs to be done
+
+_Describe the importance or impact of completing this task_
+
+
+## Timebox
+
+_How much time should be dedicated to this spike?_
+
+
+## To-do list
+
+_list out actions to be taken for this spike:_
+- [ ] 
+
+## Additional context
+
+[OPTIONAL, delete if not needed] 
+_Include any additional context or information here that doesn't fit into other parts of the template_

.github/ISSUE_TEMPLATE/task-template-aie.md

@@ -0,0 +1,37 @@
+---
+name: AIE Task Template
+about: A generic template for any task that can be adapted for multiple uses
+title: ''
+labels: aie
+assignees: ''
+
+---
+
+## What needs to be done
+
+_Provide a summary of the task that needs to be completed_
+
+
+## Why it needs to be done
+
+_Describe the importance or impact of completing this task_
+
+
+## Acceptance Criteria
+
+_List out all expected functionality/requirements_
+
+- 
+
+
+## Technical Notes
+
+_Owned by eng team - write out any important technical considerations such as: architecture plan/notes, data dependencies, testing plan, etc. Also link any tickets that are dependent on or related to this task_
+
+- 
+
+
+## Additional context
+
+[OPTIONAL, delete if not needed] 
+_Include any additional context or information here that doesn't fit into other parts of the template_

.github/ISSUE_TEMPLATE/user-story-template-aie.md

@@ -0,0 +1,48 @@
+---
+name: AIE User Story Template
+about: Create a new user story for the AIE eCR team
+title: ''
+labels: aie
+assignees: ''
+
+---
+
+## User Story
+
+As a [user/persona], I want to [do a thing], so that I can [achieve a goal/outcome]
+
+
+## Acceptance Criteria
+
+_list out all expected functionality/requirements_
+
+- 
+
+## Scenarios
+
+_Write out scenarios that will help to ensure the functionality works as expected_
+
+For example, this could look like:
+- I click on the Score filter and a dropdown appears showing a slider.
+- “1” and “10” are selected by default. The submit button is disabled.
+- I then drag the left slider to “6” making the score 6 to 10.
+- The text input below updates to display “6” and submit button is now active.
+- I click submit and the dropdown closes.
+- My search results are now updated.
+
+
+## Design Notes
+
+_Owned by design team - Attach link to design in dev mode and/or prototype, as well as any notes on visual details, interaction expectations, accessibility considerations, copy requirements_
+
+[Link to Figma design in Dev mode]()
+[Link to Figma prototype]()
+
+- 
+
+_Screenshots below should not be used for working on this ticket - always refer to Figma design for most up-to-date designs:_
+
+## Additional context
+
+[OPTIONAL, delete if not needed] 
+_Include any additional context or information here that doesn't fit into other parts of the template_