Merge branch 'working_draft' into update-subaccountID

.github/ISSUE_TEMPLATE/feedback.md

@@ -0,0 +1,78 @@
+# Feedback on Unsupported Features, Use Cases, and Existing FOCUS Spec.
+description: Provide feedback on unsupported FinOps features, use cases, or scenarios, as well as on the existing FOCUS specification content. Avoid sharing proprietary information.  
+title: "[FEEDBACK]"  
+labels: ["feedback"]  
+assignees: [shawnalpay, jpradocueva]  
+
+---
+
+### **Template Usage Notes**:
+1. All fields marked as **mandatory** [*] must be filled before submission.
+2. For **Supporting Data/Documentation**, ensure that linked files are accessible to relevant stakeholders.
+
+## 1. **Problem statement**
+Describe the problem or opportunity that this issue addresses. Explain the context and why it needs resolution.
+
+**Summary: [*]**  
+_Briefly describe the problem or opportunity that this issue addresses and why it needs resolution._  
+> **Placeholder:** Briefly describe the problem or opportunity that needs resolution.
+
+**Which area does this issue relate to? [*]**  
+_Select one of the provided options:_  
+- A: Missing FinOps feature, use case, or scenario
+- B: Existing FOCUS specification content
+- C: Other
+
+**Detailed Description [*]:**  
+_Provide a detailed description of the problem or opportunity. Add context or any other relevant information that may help in addressing this issue._  
+> **Placeholder:** Provide a comprehensive description of the problem or opportunity, including context and any relevant details.
+
+## 2. **Use Cases**
+Please describe the use cases, whether FinOps-related or otherwise, that cannot be performed with the existing specification unless this issue is addressed.
+
+**What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed? [*]**  
+_Provide detailed descriptions of the use cases that can't be performed unless this issue is addressed._  
+> **Placeholder:** List the specific use cases that can't be performed due to the existing limitations.
+
+## 3. **FinOps Personas**
+List the FinOps personas this issue relates to.
+
+**Which FinOps personas does this issue relate to? [*]**  
+_Indicate which FinOps personas this issue relates to._  
+> **Placeholder:** e.g., Practitioner, Executive, Finance, Engineering, Procurement, Operations, etc.
+
+## 4. **Providers**
+List provider groups or specific providers this issue relates to.
+
+**Which provider groups or specific providers does this issue relate to? [*]**  
+_List provider groups (e.g., CSPs, SaaS) separated by semicolons (`;`), and specific providers within those groups separated by commas (`,`). If the issue applies to all providers within a group, you can simply specify the group name (e.g., 'All CSPs')._  
+> **Placeholder:** e.g., All CSPs; SaaS: Snowflake, Salesforce
+
+## 5. **Criticality Scale**
+Indicate how critical this issue or feature request is for your organization using the scale provided below.
+
+**On a scale of 1 - 4, how critical is this for your organization? [*]**  
+_Select one of the provided options:_  
+- 1: Critical - Blocks my organization from adopting FOCUS
+- 2: Important - Ideally resolved within the next 3-6 months
+- 3: Important - Ideally resolved within the next 6-12 months
+- 4: Suggestion - Resolution not urgent
+
+## 6. **Objective**
+State the objective of this feedback. 
+- What outcome is expected?
+- Define how success will be measured (e.g., metrics and KPIs).
+
+**Objective:**  
+_Outline the expected outcome and success criteria._  
+> **Placeholder:** Outline the desired outcome and any metrics or KPIs to measure success.
+
+## 7. **Supporting Data/Documentation**
+
+**Data Examples:**  
+_Provide links to relevant sample data or attach data extracts that support your feedback. Ensure data is anonymized and does not include sensitive or proprietary information._  
+> **Placeholder:** Add link(s) to sample data or attach extracts that support your feedback.
+
+**Issues, PRs, or Other References:**  
+_Provide links to any relevant GitHub issues, pull requests, or other applicable references._  
+> **Placeholder:** Add links to any relevant GitHub issues, pull requests, or other applicable references.

.github/ISSUE_TEMPLATE/feedback.yml

@@ -1,48 +1,113 @@
-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.
+name: "Feature Request and Use Case Feedback"
+description: "Provide feedback on unsupported FinOps features, use cases, or scenarios, as well as on the existing FOCUS specification content. Avoid sharing proprietary information."
 title: "[FEEDBACK]: "
-labels: ["use case"]
-assignees: ["shawnalpay, jpradocueva,"]
+labels:
+  - "feedback"
+assignees:
+  - "shawnalpay"
+  - "jpradocueva"
 body:
   - type: markdown
     attributes:
-      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."
-
+      value: |
+        ---
+        ### **Template Usage Notes**:
+        1. All fields marked as **mandatory** [*] must be filled before submission.
+        2. For **Supporting Data/Documentation**, ensure that linked files are accessible to relevant stakeholders.
+
+
+  - type: markdown
+    attributes:
+      value: |
+        ## 1. **Problem statement**
+        Describe the problem or opportunity that this issue addresses. Explain the context and why it needs resolution.
+
+  - type: textarea
+    id: issue-summary
+    attributes:
+      label: Summary
+      description: "Briefly describe the problem or opportunity that this issue addresses and why it needs resolution."
+      placeholder: "Briefly describe the problem or opportunity that needs resolution."
+    validations:
+      required: true
+
+  - type: dropdown
+    id: issue-area
+    attributes:
+      label: Which area does this issue relate to?
+      description: "Select one of the provided options:"
+      options:
+        - 'A: Missing FinOps feature, use case, or scenario'
+        - 'B: Existing FOCUS specification content'
+        - 'C: Other'
+    validations:
+      required: true
+
   - type: textarea
+    id: issue-description
     attributes:
-      label: Proposed Change
-      description: Short description of the change and why it is necessary.
-      placeholder: Describe the proposed change briefly and why it is necessary
+      label: Detailed Description
+      description: "Provide a detailed description of the problem or opportunity. Add context or any other relevant information that may help in addressing this issue."
+      placeholder: "Provide a comprehensive description of the the problem or opportunity, including context and any relevant details"
     validations:
       required: true
-
+
+  - type: markdown
+    attributes:
+      value: |
+        ## 2. **Use Cases**
+        Please describe the use cases, whether FinOps-related or otherwise, that cannot be performed with the existing specification unless this issue is addressed.
+
   - type: textarea
+    id: use_cases
     attributes:
-      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.
+      label: What use cases, FinOps or others, can't be performed with the existing specification unless this issue is addressed?
+      description: "Provide detailed descriptions of the use cases that can't be performed unless this issue is addressed."
+      placeholder: "List the specific use cases that can't be performed due to the existing limitations."
     validations:
       required: true
 
-  - type: input
+  - type: markdown
     attributes:
-      label: Which FinOps personas perform this use case?
-      description: List one or more FinOps personas that perform this use case
-      placeholder: e.g., Cost Analyst, Cloud Architect, etc
+      value: |
+        ## 3. **FinOps Personas**
+        List the FinOps personas this issue relates to.
+
+  - type: textarea
+    id: finops-personas
+    attributes:
+      label: Which FinOps personas does this issue relate to?
+      description: "Indicate which FinOps personas this issue relates to."
+      placeholder: "e.g., Practitioner, Executive, Finance, Engineering, Procurement, Operations, etc."
     validations:
       required: true
 
-  - type: input
+  - type: markdown
+    attributes:
+      value: |
+        ## 4. **Providers**
+        List provider groups or specific providers this issue relates to.
+
+  - type: textarea
+    id: providers
     attributes:
-      label: For which providers do you perform this use case for?
-      description: List each provider separated by commas
-      placeholder: e.g., AWS, Azure, GCP, Snowflake, etc
+      label: Which provider groups or specific providers does this issue relate to?
+      description: "List provider groups (e.g., CSPs, SaaS) separated by semicolons (`;`), and specific providers within those groups separated by commas (`,`). If the issue applies to all providers within a group, you can simply specify the group name (e.g., 'All CSPs')."
+      placeholder: "e.g., All CSPs; SaaS: Snowflake, Salesforce"
     validations:
       required: true
 
+  - type: markdown
+    attributes:
+      value: |
+        ## 5. **Criticality Scale**
+        Indicate how critical this issue or feature request is for your organization using the scale provided below.
+
   - type: dropdown
+    id: criticality-scale
     attributes:
-      label: Criticality Scale
-      description: On a scale of 1 - 4, how critical is this for your organization?
+      label: On a scale of 1 - 4, how critical is this for your organization? 
+      description: "Select one of the provided options."
       options:
         - '1: Blocks my organization from adopting FOCUS'
         - '2: Important for adoption in the next 3-6 months'
@@ -51,26 +116,42 @@ body:
     validations:
       required: true
 
+  - type: markdown
+    attributes:
+      value: |
+        ## 6. **Objective**
+        State the objective of this feedback. 
+        - What outcome is expected?
+        - Define how success will be measured (e.g., metrics and KPIs).
+
   - type: textarea
+    id: objective
     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.
+      label: "Objective"
+      description: "Outline the expected outcome and success criteria."
+      placeholder: "Outline the desired outcome and any metrics or KPIs to measure success."
     validations:
       required: false
 
+  - type: markdown
+    attributes:
+      value: |
+        ## 7. **Supporting Data/Documentation**
+
   - type: textarea
+    id: data_examples
     attributes:
-      label: Context / Supporting information
-      description: Provide any other relevant information here
-      placeholder: Additional details...
+      label: "Data Examples"
+      description: "Provide links to relevant sample data or attach data extracts that support your feedback. Ensure data is anonymized and does not include sensitive or proprietary information."
+      placeholder: "Add link(s) to sample data or attach extracts that support your feedback."
     validations:
-      required: true
+      required: false
 
   - type: textarea
+    id: issue_pr_references
     attributes:
-      label: Data Submission for Discussion
-      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.
+      label: "Issues, PRs, or Other References"
+      description: "Provide links to any relevant GitHub issues, pull requests, or other applicable references."
+      placeholder: "Add links to any relevant GitHub issues, pull requests, or other applicable references."
     validations:
-      required: false  
+      required: false