Update feedback use case

.github/ISSUE_TEMPLATE/feedback.yml

@@ -1,12 +1,12 @@
-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, udam-f2, 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
  attributes:
@@ -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,55 @@ body:
  validations:
  required: true
 
+ - type: textarea
+ attributes:
+ label: Business and Financial Objectives
+ description: Describe the business and financial objectives this use case aims to achieve.
+ placeholder: Describe the expected business and financial outcomes.
+ validations:
+ required: false
+
+ - type: input
+ attributes:
+ label: Cost Drivers
+ description: Identify the primary cost drivers related to this use case (e.g., cloud spending, infrastructure costs).
+ placeholder: e.g., cloud spending, infrastructure costs, etc.
+ validations:
+ required: false
+
+ - 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: input
+ attributes:
+ label: Expected Financial Impact
+ description: Quantify the expected financial impact, if applicable (e.g., percentage cost savings, budget reductions).
+ placeholder: e.g., 10% cost savings, 5% budget reduction, etc.
+ validations:
+ required: false
+
+ - type: textarea
+ attributes:
+ label: Testing Approach
+ description: Outline how the use case will be tested before full implementation. Specify the types of testing (e.g., pilot testing, A/B testing).
+ placeholder: Describe your testing approach.
+ validations:
+ required: false
+
+ - type: textarea
+ attributes:
+ label: Validation Criteria
+ description: Define how success will be validated after implementation. Include metrics that will be reviewed post-implementation.
+ placeholder: e.g., metrics to validate success, financial impact, etc.
+ validations:
+ required: false
+
+
  - type: textarea
  attributes:
  label: Context / Supporting information
@@ -65,5 +114,5 @@ body:
  description: Provide relevant sample data or data extracts that support your feedback. Ensure data is anonymized and does not include sensitive or proprietary information.
  placeholder: Attach sample data or data extracts here. Ensure compliance with data privacy guidelines.
  validations:
- required: false 
+ required: true