Update and rename vro-request.md to vro-request.yml

.github/ISSUE_TEMPLATE/vro-request.yml

@@ -0,0 +1,83 @@
+name: VRO request
+description: Request a service or functionality from VRO
+title: "[Request]: "
+labels: ["request", "triage"]
+projects: ["department-of-veterans-affairs/871"]
+assignees:
+  - dianagriffin
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **When to use this template**
+        For existing partner teams, this form is to help the VRO Team understand how their platform can best support your solution. Please answer all questions to the best of your ability before submitting the request. 
+        - If your team has not worked with VRO previously, please reach out to **@vro-team** in [#benefits-vro-support](https://dsva.slack.com/archives/C01Q7979Z7D) to share a bit about your interest in VRO and we'll respond with next steps.
+
+        **What to expect when submitting a request**
+        Generally, someone from the VRO Team will respond back within 48 hours acknowledging the receipt of your request. 
+        - If the request is small and straightforward they will let you know what Sprint the work can be prioritized in and when you can anticipate the work to be completed.
+        - If the request is large they may ask additional questions and/or invite you and your team to a joint feature refinement session. After the feature is refined and split into user stories they can provide a timeline for when the work is anticipated to be completed. 
+  - type: input
+    id: team
+    attributes:
+      label: Requesting Team
+      description: Which partner team are you requesting on behalf of? 
+      placeholder: ex. Employee Experience
+    validations:
+      required: true
+  - type: input
+    id: initiative
+    attributes:
+      label: Related product/initiative
+      description: Which of your team's products or initiatives does this request relate to? 
+      placeholder: ex. Monitoring solution
+    validations:
+      required: false 
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem/Need
+      description: Please describe the problem or need your team is facing and how you anticipate a VRO service or functionality could meet that need
+      placeholder: Tell us what you need
+    validations:
+      required: true
+  - type: textarea
+    id: value
+    attributes:
+      label: Why?
+      description: Why is this need important, and what value will it provide to your users/stakeholders? What is your hypothesis for this solution?
+      placeholder: Tell us why you need it
+    validations:
+      required: true
+  - type: textarea  
+    id: ac
+    attributes:
+      label: Acceptance criteria
+      description: Please detail how your team will test that the VRO team completed your request as expected? List all known acceptance criteria.
+      placeholder: How do your engineers anticipate interacting with the VRO solution? Who can the VRO team reach out to for shared testing efforts?
+    validations:
+      required: true
+  - type: textarea
+    id: priority
+    attributes:
+      label: Priority
+      description: What is your team's priority for addressing this problem? Do you have any alternatives to get your need met?
+      placeholder: Tell us how urgently you need it
+    validations:
+      required: true
+  - type: textarea
+    id: timeline
+    attributes:
+      label: Target timeline
+      description: Do you have a target timeline for this solution? Why are you aiming for that timeline?
+      placeholder: Tell us when you're hoping to have this solution
+    validations:
+      required: false
+  - type: textarea
+    id: notes
+    attributes:
+      label: Context and documentation
+      description: Please share any additional context and/or link any relevant documentation or artifacts you have in relation to your request.
+      placeholder: What else should we know about this request?
+    validations:
+      required: false