Update feedback use case (#553)

This PR suggests updating the current GitHub Issue "feedback" template.
The proposed changes are aligned with the proposal [24.09.23 FOCUS
Process
Improvements](https://docs.google.com/document/d/1W10WbS3JzGio2zrWzytxkvvRigE8hBmfyCS9Vcx6wVw/edit?usp=sharing):
* This proposal outlines improvements to the FOCUS Development Process,
aligning it with best practices commonly adopted by standards
organizations. While FOCUS has successfully implemented most lifecycle
stages, the Work Item phase remains unaddressed.
* The proposal aims to provide a clear starting point for group
discussions, offering the following key recommendations:
A structured process for Work Item creation.
An improvement to the existing [FinOps Use Case Feedback]() (GitHub
Issue)
Enhancements to the Review & Approval process introduce a requirement
that any objection must include a written rationale.

.github/ISSUE_TEMPLATE/feedback.yml

@@ -1,14 +1,14 @@
-name: FinOps Use Case Feedback
-description: Provide feedback on FinOps use cases that cannot be performed with the current FOCUS specification.
+name: Feature Request and Use Case Feedback
+description: Provide feedback on unsupported use cases or features in the FOCUS specification, including FinOps scenarios, to help prioritize updates. Avoid sharing proprietary information.
 title: "[FEEDBACK]: "
-labels: [""]
-assignees: ["mike-finopsorg,udam-f2"]
+labels: ["use case"]
+assignees: ["shawnalpay, jpradocueva,"]
 body:
   - type: markdown
     attributes:
-      value: "The FOCUS working group wants to understand what FinOps use cases cannot be performed today using the current specification so they can be prioritized for upcoming release. Please do not provide any information that may be considered Intellectual Property by any individual or organization."
+      value: "FOCUS working group seeks gaps in the current specification for FinOps and beyond. Share unsupported use cases or features to prioritize updates. Avoid sharing proprietary information."
 
-  - type: input
+  - type: textarea
     attributes:
       label: Proposed Change
       description: Short description of the change and why it is necessary.
@@ -18,8 +18,8 @@ body:
 
   - type: textarea
     attributes:
-      label: What FinOps use cases cannot be performed without the proposed change?
-      description: Describe in detail the current FinOps use cases your organization cannot perform without the proposed change
+      label: What use cases, FinOps or others, can't be performed with the current specification without this change?
+      description: Describe in detail the use cases, whether FinOps-related or otherwise, that your organization cannot perform with the current specification without the proposed change.
     validations:
       required: true
 
@@ -51,6 +51,14 @@ body:
     validations:
       required: true
 
+  - type: textarea
+    attributes:
+      label: Key Metrics and KPIs
+      description: List the metrics and KPIs that will measure the success of this use case (e.g., cost per service, spend reduction percentage).
+      placeholder: e.g., cost per service, spend reduction percentage, etc.
+    validations:
+      required: false
+
   - type: textarea
     attributes:
       label: Context / Supporting information
@@ -66,4 +74,3 @@ body:
       placeholder: Attach sample data or data extracts here. Ensure compliance with data privacy guidelines.
     validations:
       required: false  
-