Census Use Case

Activate your data in GitHub to automatically track issues

Learn how to automate issue tracking and collaborate more effectively with your team using GitHub and Census.


Issue tracking is crucial for any engineering team, but managing issues can be a tedious and manual process — especially when you’re dealing with a huge volume of data.

What if… you could automate this process and make it more efficient?

That's where creating GitHub issues with data from across your organization comes in. This approach allows you to automatically track issues and collaborate with your team — no matter where they come from — all while saving valuable time and effort.

As an added bonus, you’ll experience benefits like:

  1. Collaborate effectively: With GitHub issues, you can collaborate with your team by assigning issues to specific team members and communicating through comments. This promotes collaboration and ensures that everyone is on the same page.
  2. Improve prioritization: Using the priority field, you can prioritize issues based on their level of importance. This helps you focus on the most critical issues and ensures that they are addressed promptly.
  3. Gain insights: By analyzing the data in your data warehouse, you can gain insights into recurring issues and their root causes. This helps you identify areas for improvement and prevent future issues.

The best part is you can implement this solution using Census! Below are the ten customer fields that you need to create issues in GitHub:

Customer Field Name Field Description
title A brief summary of the issue
description A detailed description of the issue
assignees The person(s) responsible for the issue
labels Categorize issues with labels
milestone Group related issues together
project The project associated with the issue
priority The level of importance of the issue
type The type of issue (e.g., bug, feature request, etc.)
status The current status of the issue
due_date The due date of the issue

Use Case

Now that you know the benefits of creating GitHub issues with data from your data warehouse, let's walk through the two, simple steps to set it up.

  1. Map your data fields: Map your data fields to the customer fields mentioned above to ensure that the data is properly recorded in GitHub.
  2. Create issues: Use Census to create GitHub issues with data from your data warehouse. You can use models in Census to ensure that only relevant data is sent to GitHub.

What's next?

Now that you've learned how to create GitHub issues with data from your data warehouse, you can use this approach to track customer support tickets, track product feedback, or even monitor your team's progress on specific projects.

Destination Guides

Unsure how to implement your use case?
Schedule a call with us to discuss!