Skip to content

Issues: FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec

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

62 Open 164 Closed
62 Open 164 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[EDITORIAL] Editorial Style Reference (Proposal) discussion topic Item to be discussed by the community (can be used for questions as well)
#476 opened May 31, 2024 by jpradocueva v1.1
Provide example of difference between Charge and Billing Period discussion topic Item to be discussed by the community (can be used for questions as well)
#475 opened May 31, 2024 by dinoboy197 v1.1
SKU / SKU Price Details-related issues - backlog cleanup discussion topic Item to be discussed by the community (can be used for questions as well)
#473 opened May 28, 2024 by ijurica v1.1
Billing dataset or FOCUS dataset - terminology, definition and metadata requirements discussion topic Item to be discussed by the community (can be used for questions as well) editorial Items that address editorial and minor changes
#472 opened May 24, 2024 by ijurica v1.1
Possible Scope Themes for v1.1 discussion topic Item to be discussed by the community (can be used for questions as well)
#467 opened May 17, 2024 by jpradocueva v1.1
Derived charges (such as '%' of other charges) in the billing dataset discussion topic Item to be discussed by the community (can be used for questions as well) P2 Minor improvement or low-priority use case blocked
#466 opened May 16, 2024 by ijurica v1.1
GitHub Team Access Rights Proposal discussion topic Item to be discussed by the community (can be used for questions as well)
#465 opened May 16, 2024 by jpradocueva v1.1
Branches Status discussion topic Item to be discussed by the community (can be used for questions as well) repo maintenance Issues related to maintenance tasks on the repo
#464 opened May 16, 2024 by jpradocueva
21 of 44 tasks
v1.1
1
Proposal for Revision of Labeling and Qualification System discussion topic Item to be discussed by the community (can be used for questions as well)
#462 opened May 15, 2024 by jpradocueva v1.1
1
Add different pricing scenarios in Appendix discussion topic Item to be discussed by the community (can be used for questions as well) P2 Minor improvement or low-priority use case blocked
#440 opened May 7, 2024 by marc-perreaut v1.1
@udam-f2
1
Should FOCUS try to update language in the spec where it _may_ be considered jargon discussion topic Item to be discussed by the community (can be used for questions as well) P3 Nice to have in the release
#437 opened May 6, 2024 by udam-f2 v1.1
@udam-f2
Is FOCUS use of "Service" aligned with the FinOps tools and services capability? P3 Nice to have in the release
#414 opened Apr 22, 2024 by flanakin
1 task done
v1.1
1
@mike-finopsorg @udam-f2
3
Add a Commitment-Based Coverage column to rows that are or potentially can be covered by a Commitment. P2 Minor improvement or low-priority use case blocked
#406 opened Apr 18, 2024 by cnharris10 v1.1
1
@cnharris10 @aqu-erp
2
Add support for sub categorizations of ServiceCategory P1 Significant improvement in clarity (ambiguous otherwise) or high-priority use case blocked
#404 opened Apr 16, 2024 by udam-f2 v1.1
@aqu-erp
3
How to represent ODCRs in FOCUS discussion topic Item to be discussed by the community (can be used for questions as well) P2 Minor improvement or low-priority use case blocked
#397 opened Apr 13, 2024 by AWS-ZachErdman v1.1
@ijurica @gparker-at-sf
2
Update to allowed ServiceCategory values P1 Significant improvement in clarity (ambiguous otherwise) or high-priority use case blocked
#379 opened Apr 3, 2024 by AWS-ZachErdman v1.1
1
@projectlocale @mike-finopsorg
@rupagcp @SonalGarg-SG
13
Within a billing month dataset partition, explicitly state all included columns/properties must be present in all rows. P1 Significant improvement in clarity (ambiguous otherwise) or high-priority use case blocked
#374 opened Mar 28, 2024 by cnharris10 v1.1
@rileyjenk @projectlocale @cnharris10
2
Enhanced consistency in ResourceType and ServiceName across a resourceId-related charge records discussion topic Item to be discussed by the community (can be used for questions as well) P3 Nice to have in the release
#359 opened Mar 11, 2024 by ijurica v1.1
@projectlocale @cnharris10
2
[FEEDBACK]: Does FOCUS standard is planning to support the licenses costs acquired thru a CSP Marketplace of thru another ways interfaced with the CSP ? P2 Minor improvement or low-priority use case blocked
#358 opened Mar 8, 2024 by PE-Nuiry v1.2
@mike-finopsorg @udam-f2 @SonalGarg-SG
1
[Proposal] Separation of Tags and Labels P3 Nice to have in the release
#356 opened Mar 7, 2024 by ahullah v1.1
@ahullah @SonalGarg-SG
2
Add a indication of mutability to the content contraints of each column discussion topic Item to be discussed by the community (can be used for questions as well) P2 Minor improvement or low-priority use case blocked
#351 opened Mar 4, 2024 by silvexis v1.1
@silvexis @SonalGarg-SG
3
[Content Suggestion] Clarify what is included in FOCUS "Amortization" discussion topic Item to be discussed by the community (can be used for questions as well) P1 Significant improvement in clarity (ambiguous otherwise) or high-priority use case blocked
#344 opened Feb 28, 2024 by AWS-ZachErdman v1.1
@flanakin @rileyjenk
@mike-finopsorg @rupagcp @AWS-ZachErdman @SonalGarg-SG
6
[Content Suggestion] FOCUS line item examples discussion topic Item to be discussed by the community (can be used for questions as well) P1 Significant improvement in clarity (ambiguous otherwise) or high-priority use case blocked
#341 opened Feb 28, 2024 by AWS-ZachErdman v1.1
@rileyjenk @udam-f2 @ijurica
3
[Proposal] Add support for describing different types of usage of a single product. P1 Significant improvement in clarity (ambiguous otherwise) or high-priority use case blocked
#339 opened Feb 28, 2024 by AWS-ZachErdman
2 tasks
v1.1
@flanakin @rileyjenk
8
[Proposal] Handling non currency cost and usage pricing models. P2 Minor improvement or low-priority use case blocked
#337 opened Feb 28, 2024 by rileyjenk
3 tasks
v1.1
@flanakin @rileyjenk
6
ProTip! Mix and match filters to narrow down what you’re looking for.