Billing UX for Applications
Open
area:billing
task
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 146
Description
### Description
With #1689 we are introducing `Application` as a top level concept that contains multiple Instances (aka Projects in our current language).
With billing done at the Team level (above Application) we need to think about how billing information is presented to the user to reflect application/instances. As it stands, they will just have a count of instances across the whole team, without any information on where those costs are coming from between their different applications.
### Epic/Story
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.