Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update feedback use case #553

Merged
merged 8 commits into from
Oct 11, 2024
Merged

Update feedback use case #553

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
7bf5232
update to feedback template based on FinOps staff discussion
jpradocueva Sep 26, 2024
b546c50
reduce descriptions below 200 characters
jpradocueva Sep 26, 2024
514858f
Update .github/ISSUE_TEMPLATE/feedback.yml
jpradocueva Sep 30, 2024
ee12620
remove udam
jpradocueva Oct 9, 2024
93376e4
updates to feedback
jpradocueva Oct 9, 2024
e462d1f
updates to feedback
jpradocueva Oct 9, 2024
0f77f16
Update .github/ISSUE_TEMPLATE/feedback.yml
jpradocueva Oct 10, 2024
7a6b4be
Merge branch 'working_draft' into update-feedback-use-case
jpradocueva Oct 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 16 additions & 9 deletions .github/ISSUE_TEMPLATE/feedback.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
jpradocueva marked this conversation as resolved.
Show resolved Hide resolved
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: [""]
shawnalpay marked this conversation as resolved.
Show resolved Hide resolved
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.
Expand All @@ -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

Expand Down Expand Up @@ -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
Expand All @@ -66,4 +74,3 @@ body:
placeholder: Attach sample data or data extracts here. Ensure compliance with data privacy guidelines.
validations:
required: false

Loading