When a new issue is added to GitHub, Process Street can trigger a checklist. For example, in this article we’ll look at a zap that triggers a debugging checklist in Process Street when a new issue with the ‘bug’ label is added in GitHub.
With this integration, you’ll be able to keep track of your in-progress bugs, and follow a structured process to keep your debugging consistent.
- A company tracks bugs in GitHub
- For each new bug, the company wants to run a debugging checklist to help improve consistency or train a new developer
- We will create a zap that connects GitHub issues to Process Street
- We will filter the zap’s conditions to only trigger a checklist when an issue is labelled ‘bug’
- Details from GitHub will be automatically filled into the checklist to keep information centralized
Let’s get started.
Add the software debugging template to your Process Street account
We have plenty of software templates inside Process Street.
You can use any of them, or create your own from scratch. But, for this tutorial, we’ve selected an easy example to demonstrate.
We’re going to use our pre-made debugging template which you can grab below:
Create a zap to connect GitHub and Process Street
Choose your trigger as GitHub, and select “New Issue”. You can optionally set the issue trigger to fire only when the issue is in a particular repo or assigned to a particular user.
For this zap, we only want the checklist to fire when the issue is a bug. The issue is marked as a bug by labeling it as such in GitHub, so all we have to do is add a filter step to Zapier. Click the plus on the left sidebar, and add a filter like this:
Now the zap only passes data onto Process Street if the filter conditions are met.
Configure the zap to pass data to Process Street checklist form fields
Keep your data centralized by pushing GitHub data to Process Street. This saves the developer from switching between two different environments to get information.
Set up Process Street as the zap’s action step, with “Create Checklist” selected.
The two required fields in the “Edit Template” screen are template and name. Set the template to your newly-added Software Debugging template, and the name to the issue title.
You can do this by clicking the arrow next to the field name in Zapier, and selecting from Process Street and GitHub variables.
Matching the checklist title to the issue title is useful, but you can also include the issue ID and description because the Process Street template has form fields designated for that data.
Scroll further down the “Edit Template” screen of the zap, and you’ll see those fields:
Continue through the zap setup, and you’ll be able to test whether the GitHub issue data is being sent to Process Street. If everything is working so far, you can go into Process Street and see your new checklist run: