Issue template updates

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,56 @@
+name: Bug report
+description: Create a report of a defect on the live service, so we can investigate.
+title: "[BUG] <title>"
+labels: ["bug"]
+projects: ["gigascience/71"] 
+assignees:
+  - pli888
+  - kencho51
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug
+      description: Please provide a clear and concise description of what the bug is.
+      placeholder: e.g. When I do X, Y happens.
+  - type: textarea
+    id: To_Reproduce
+    attributes:
+      label: To Reproduce
+      description: Please provide a list of steps to reproduce the issue.
+      placeholder: |
+        Steps to reproduce the behavior:
+        1. Go to '...'
+        2. Click on '....'
+        3. Scroll down to '....'
+        4. See error
+  - type: textarea
+    id: Expected_behavior
+    attributes:
+      label: Expected behavior
+      description: Please provide a clear and concise description of what you expected to happen.
+      placeholder: What should happen?
+  - type: textarea
+    id: Screenshots
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots to help explain your problem.
+  - type: textarea
+    id: device_information
+    attributes:
+      label: device information
+      placeholder: |
+        Desktop (please complete the following information)
+         - OS: [e.g. iOS]
+         - Browser [e.g. chrome, safari]
+         - Version [e.g. 22]
+        Smartphone (please complete the following information)
+         - Device: [e.g. iPhone6]
+         - OS: [e.g. iOS8.1]
+         - Browser [e.g. stock browser, safari]
+         - Version [e.g. 22]
+  - type: textarea
+    id: Additional_context
+    attributes:
+      label: Additional context
+      placeholder: Add any other context about the problem here.

.github/ISSUE_TEMPLATE/product_backlog_item.yaml

@@ -0,0 +1,54 @@
+name: Product Backlog Item
+description: Create a user story and acceptance criteria for feature requests and updates to go in the product backlog
+labels: ['backlog:Story']
+projects: ["gigascience/71"] 
+body: 
+  - type: textarea
+    id: user_story
+    attributes:
+      label: User Story
+      description: Please provide a user story(s) for the feature
+      placeholder: |
+        >As a user  
+        >I want something implemented  
+        >So that I can benefit
+  - type: textarea
+    id: Acceptance_criteria
+    attributes:
+      label: Acceptance criteria
+      description: Please provide acceptance criteria for the story, enter as many as required.
+      placeholder: |
+        >Given conditions  
+        >When event  
+        >Then outcome
+  - type: textarea
+    id: Additional_Info
+    attributes:
+      label: Additional Info
+      description: Please provide any additional information about the feature here, include links to related issues.
+  - type: checkboxes
+    id: Product_Backlog_Item_Ready_Checklist
+    attributes:
+      label: Product Backlog Item Ready Checklist
+      options:
+        - label: Business value is clearly articulated
+        - label: Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
+        - label: Dependencies are identified and no external dependencies would block this item from being completed
+        - label: At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
+        - label: This item is estimated and small enough to comfortably be completed in one sprint
+        - label: Acceptance criteria are clear and testable
+        - label: Performance criteria, if any, are defined and testable
+        - label: The Scrum team understands how to demonstrate this item at the sprint review
+  - type: checkboxes
+    id: Product_Backlog_Item_Done_Checklist
+    attributes:
+      label: Product Backlog Item Done Checklist
+      options:
+        - label: Item(s) in increment pass all Acceptance Criteria
+        - label: Code is refactored to best practices and coding standards
+        - label: Documentation is updated as needed
+        - label: Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
+        - label: No deviation from the team technology stack and software architecture has been introduced
+        - label: The product is in a releasable state (i.e. the increment has not broken anything)
+
+