Feature Requests

We're rolling out a new "Compare" page in your plan settings that lets you visualize and compare your credit consumption across the past few billing cycles. With this page you can: See trends in how your spend has changed over time Compare usage at the plan level or drill down into individual projects Filter by charge type (e.g., compute, users, network) You'll find it as a new tab in your plan settings navigation. This is a beta feature, so we'd love your feedback on what's useful, what's missing, and how we can make it better. Drop your thoughts here!

The Plans page has a UI with a lot of useful information regarding credit utilization, user, network and storage usage information. It will be nice to fetch these information via an API for reporting purposes.

When building public projects on the Performance Plan, all builds will use paid credits. This document ( https://circleci.com/docs/2.0/oss/#overview ) states customers are given 100,000 free credits per week for their open source projects, but this is only applicable to users on the free plan. This is clarified here: https://support.circleci.com/hc/en-us/articles/360038512113--How-does-CircleCI-charge-credits-for-Private-and-Public-Repositories- Users who are building on open source and private repositories will count against the number of user seats available for the billing cycle.

adds cost transparency. allows us to know which builds are expensive and should prioritize optimization. CCI-I-1590

Presently the available build minutes in organisations are only available to BB/GH admins. However, it is often team members who bring in a CI solution. My recent experience has been to spin up some CI solutions on the free tier, in the hope that the reliability improvements brought in by effective CI encourage a business case to be made around CircleCI. Part of this initial free tier experience is keeping an eye on build minutes, so that the team do not run out mid-month. I don't think it is secret information and there would be no reason to withhold it from non-admins. CCI-I-881

There should be a way to set a thresh-hold for available credits to send an email when they get to a certain amount to help remind people to top up their credits before they run out. This should be available under plan with a configurable list of email addresses that should be contacted.

The new performance plan eliminates queueing and provides flexible resource allocation, but customers often want to throttle or limit particular project's share in the overall resource pool.This is to request project based credit limits or quotas that would block or shape requests from specific projects if they go over a defined limit. CCI-I-624

Some users are charged for a seat even when their activity is limited to feature or environment branches. Current configurations require builds to trigger on all branches, and jobs are then canceled in the config if they don’t match specific branch patterns. Although these builds exit immediately, the users are still counted as active seats.

Allow annualized customers the ability for teams/projects to have their own credit balance/usage under one annualized contract. Each team/project would have their own LMK for auto-refill and would not be able to use other team/project's credits, they'd need to buy more on their own when credit balance is low. This would prevent internal billing issues for ENT/COMM customers and improve their internal usage projections.

cannot get any help when I try to make payment. should have a direct support. I try to add a billing account for our company's accountant (who doesn't use github), but she cannot see the settings to make the payment. CCI-I-776