Create issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,59 @@
+---
+name: Bug report
+about: Template for reporting a bug in the VA mobile design system
+title: BUG - [SEVERITY] - [iOS/Android/All] - [Short description]
+labels: bug, design-system
+assignees: ''
+
+---
+
+<!-- Please fill out all of the relevant sections of this template.  -->
+## What happened?
+<!-- General overview of what happened and where it happened -->
+
+## Specs:
+<!-- What are the specifics that are important to this issue? Delete anything that isn't important -->
+- Device:
+- OS:
+- User Account:
+- Accessibility State:
+
+## Steps to Reproduce
+<!-- Step by step instructions on how to reproduce. BE AS SPECIFIC AS POSSIBLE -->
+
+## Desired behavior
+<!-- What *should* have happened -->
+
+## Acceptance Criteria
+<!-- What is/are the requirements for fixing the bug? If this bug was found without a ticket, leave blank. It should be filled in during the next bug scrub. -->
+
+## Bug Severity - BE SURE TO ADD THE SEVERITY LABEL
+<!-- How bad is it? --> 
+See [Bug Tracking](https://department-of-veterans-affairs.github.io/va-mobile-app/docs/QA#issue-severity) for details on severity levels
+<!-- Pick high or low for each category, using definitions in the link above if needed. -->
+- Impact: High Low 
+- Frequency: High Low 
+
+<!-- Pick a single severity label (and delete the others) -->
+<!-- sev-1 is HIGH for both impact and frequency, sev-2 is HIGH in one measure and LOW in the other, sev-3 is LOW for both -->
+- 3 - Low
+- 2 - High
+- 1 - Critical
+
+## Linked to Story
+<!-- OPTIONAL. Add the link to the issue here. you can shorthand the link like this: #598 where 598 is the ticket number. Skip if found during a regression. -->
+
+## Screen shot(s) and additional information
+<!-- Add any screen shots, video, gifs, etc that will help the engineers track down the issue. The 'details' section below will expand/collapse, so is a good default location for long JSON responses.  -->
+
+<details>
+  <summary>Full JSON response for services related to issue (expand/collapse)</summary>
+  <!-- Copy-paste the JSON from Charles here. Easiest is to use the 'raw' tab which will include header + body. -->
+
+</details>
+
+## Ticket Checklist
+- [ ] Steps to reproduce are defined
+- [ ] Desired behavior is added
+- [ ] Labels added (front-end, back-end, relevant feature, accessibility, etc)
+- [ ] Estimate of 1 added (for front-end tickets)