How to Route Bug Reports from GitHub to Jira with Pipedream

Workflows > New > Workflow

Create new workflow

Log into pipedream.com and click the blue New button in the top right. Select Workflow from the dropdown menu. You'll land on a blank workflow canvas with a trigger step already added at the top.

1. 1Click New in the top navigation
2. 2Select Workflow from the dropdown
3. 3You'll see an empty trigger step

Trigger > GitHub > New Issue Event

Add GitHub webhook trigger

Click on the trigger step and search for GitHub in the app list. Select 'New Issue Event' from the available triggers. This creates a webhook endpoint that GitHub will call whenever issue events happen in your repository.

1. 1Click the trigger step
2. 2Search for 'GitHub' in the app selector
3. 3Choose 'New Issue Event' from the trigger list
4. 4Click Continue

GitHub Trigger > Connect Account

Connect GitHub account

Click Connect Account and authorize Pipedream to access your GitHub repositories. After OAuth completes, select your target repository from the Repository dropdown. Choose 'issues' from the Events field to only listen for issue-related changes.

1. 1Click Connect Account
2. 2Complete GitHub OAuth in the popup
3. 3Select your repository from the dropdown
4. 4Set Events to 'issues'

Add Step > Filter

Add filter for bug labels

Click the plus icon below your trigger to add a new step. Search for 'Filter' and select it. This prevents the workflow from running on every GitHub issue event. You only want it to proceed when the action is 'labeled' and the label name is 'bug'.

1. 1Click the + icon below the trigger
2. 2Search for 'Filter'
3. 3Select the Filter step
4. 4Set condition to continue only if specific criteria match

Filter > Conditions

Configure bug label condition

In the filter condition, set the first dropdown to 'steps.trigger.event.action' and choose 'equal to'. Type 'labeled' in the value field. Add a second condition where 'steps.trigger.event.label.name' equals 'bug'. Set the logic to AND so both conditions must be true.

1. 1Set first condition: action equals 'labeled'
2. 2Click Add Condition
3. 3Set second condition: label.name equals 'bug'
4. 4Change logic operator to AND

Add Step > Code > Run Node.js Code

Add severity mapping code step

Add another step and choose 'Run Node.js Code'. This step will examine the GitHub issue labels and map them to Jira severity levels. GitHub might use labels like 'critical', 'high', 'medium' that need conversion to Jira's priority scheme.

1. 1Click + to add another step
2. 2Select 'Run Node.js Code'
3. 3Name the step 'Map Severity'
4. 4Clear the default code

This code examines all GitHub issue labels and maps severity indicators to Jira priorities. Paste it in the Node.js code step between the filter and Jira creation.

export default defineComponent({
  async run({ steps, $ }) {
    const issue = steps.trigger.event.issue;

export default defineComponent({
  async run({ steps, $ }) {
    const issue = steps.trigger.event.issue;
    const labels = issue.labels?.map(l => l.name.toLowerCase()) || [];
    
    // Map GitHub labels to Jira priorities
    let priority = 'Medium'; // default
    if (labels.includes('critical') || labels.includes('p0')) {
      priority = 'Highest';
    } else if (labels.includes('high') || labels.includes('p1')) {
      priority = 'High';
    } else if (labels.includes('low') || labels.includes('p3')) {
      priority = 'Low';
    }
    
    // Extract additional context
    const severity = labels.find(l => l.startsWith('severity-'));
    const component = labels.find(l => l.startsWith('component-'));
    
    return {
      title: issue.title,
      description: `${issue.body}\n\nGitHub Issue: ${issue.html_url}\nReporter: ${issue.user.login}`,
      priority,
      severity,
      component: component?.replace('component-', ''),
      originalLabels: labels,
      githubId: issue.id
    };
  }
});

Code Step > Editor

Write severity mapping logic

Replace the default code with logic that checks all labels on the GitHub issue and converts them to Jira priority names. The code should return both the mapped priority and extract other useful fields like title and description for the Jira ticket.

1. 1Delete the template code
2. 2Paste the severity mapping code
3. 3Update the label names to match your GitHub setup
4. 4Test with sample data

Add Step > Jira > Create Issue

Add Jira create issue step

Add a new step and search for Jira. Select 'Create Issue' from the available actions. This step will take the mapped data from your code step and create the actual bug ticket in your Jira project.

1. 1Click + to add a step
2. 2Search for 'Jira'
3. 3Choose 'Create Issue' action
4. 4Click Continue

Jira Step > Connect Account > Configure Issue

Connect Jira and configure project

Connect your Jira account through OAuth or API token depending on your Jira type. Once connected, select your target project from the Project dropdown. Set Issue Type to 'Bug' and map the Summary field to the GitHub issue title from your trigger data.

1. 1Click Connect Account and complete Jira auth
2. 2Select your project from the dropdown
3. 3Set Issue Type to 'Bug'
4. 4Map Summary to GitHub issue title

Jira Step > Field Mapping

Map remaining Jira fields

Fill out the Description field with the GitHub issue body text. Set Priority using the mapped severity from your code step. Add the GitHub issue URL to a custom field or in the description so your team can reference the original report.

1. 1Map Description to GitHub issue body
2. 2Set Priority from code step output
3. 3Add GitHub URL to description or custom field
4. 4Configure any required custom fields

Test > Select Event Data

Test the workflow

Click the Test button in the top right to run your workflow with sample data. If you don't see recent GitHub events in the test data dropdown, go create a test issue in GitHub, add the 'bug' label, then come back and test. Check that your Jira project shows the new bug ticket.

1. 1Click Test in the top navigation
2. 2Select a recent GitHub issue event
3. 3Click Run Test
4. 4Check Jira project for new ticket