Skip to main content
Turn an anomaly or a recommendation into a GitHub issue in one step. The issue carries the cost detail and a link back to CostGraph. The CostGraph page then shows Open #123 for that issue. Issues go through the CostGraph GitHub App, the same app that reads GitHub billing. GitHub issues work on self-hosted deployments too.

​
Before you begin

  • A CostGraph organization owner or admin to choose repositories.
  • An owner of the GitHub organization to approve the app’s Issues permission.

​
Approve the issues permission

The CostGraph GitHub App asks for permission to create issues. If your organization installed the app before it asked for this, GitHub shows a request to approve the updated permissions. An owner of the GitHub organization must approve it in GitHub. Until an owner approves, CostGraph asks for that approval instead of creating the issue.

​
Connect GitHub issues

1

Install the GitHub App

Connect GitHub with the CostGraph GitHub App if you have not already. The GitHub card then appears in the Ticketing section of Settings > Integrations.
2

Choose repositories

On the GitHub card, click Choose where tickets go. Select the repositories people may create issues in, then click Save. Only private repositories are listed, which keeps cost detail out of public issues.
To change the list later, click Choose where tickets go on the GitHub card again.

​
Create an issue

  1. Open an anomaly or a recommendation.
  2. Click Create ticket and select GitHub.
  3. Choose the repository for the issue. CostGraph creates it and shows Open #123.
Each anomaly or recommendation has at most one GitHub issue. Choosing GitHub again opens the existing issue instead of creating another one.

​
Disconnect

GitHub issues stop when the CostGraph GitHub App is disconnected or uninstalled. Issues already created stay in GitHub.