How to sync PR to Jira status with Pipedream

Pipedream Dashboard > Workflows > New

Create new Pipedream workflow

Go to pipedream.com and click New Workflow in the top navigation. You'll land on the workflow builder with a blank canvas. The interface shows Steps on the left and the configuration panel on the right. Click the Add a Trigger button to start building.

1. 1Click 'New Workflow' in the top navigation
2. 2Click 'Add a Trigger' in the workflow builder
3. 3Search for 'GitHub' in the app selector
4. 4Select 'New Pull Request' from the trigger list

Trigger Configuration > GitHub > New Pull Request

Configure GitHub webhook trigger

Connect your GitHub account by clicking Connect Account. Select your repository from the dropdown - this determines which repo will send webhook events. Choose 'Pull Request opened' as the event type. Pipedream automatically creates a webhook endpoint that GitHub will call.

1. 1Click 'Connect Account' and authorize Pipedream
2. 2Select your target repository from the dropdown
3. 3Choose 'opened' from the pull request events
4. 4Click 'Save' to create the webhook

Workflow Builder > Add Step > Code

Add code step to extract Jira ticket key

Click Add a Step below the trigger and select Code. This Node.js step will parse the branch name to find Jira ticket keys. The GitHub webhook payload includes the branch name in the head.ref field. You'll write JavaScript to extract patterns like PROJ-123 from branch names.

1. 1Click '+ Add a Step' below the GitHub trigger
2. 2Select 'Code' from the step types
3. 3Choose 'Run Node.js code'
4. 4Name the step 'Extract Jira Key'

This code extracts Jira ticket keys from branch names and handles multiple project prefixes. Paste this in your Node.js code step to replace the default template.

export default defineComponent({
  async run({ steps, $ }) {
    const branchName = steps.trigger.event.pull_request.head.ref;

export default defineComponent({
  async run({ steps, $ }) {
    const branchName = steps.trigger.event.pull_request.head.ref;
    const prTitle = steps.trigger.event.pull_request.title;
    const prUrl = steps.trigger.event.pull_request.html_url;
    const author = steps.trigger.event.pull_request.user.login;
    
    // Match Jira ticket patterns like PROJ-123, AUTH-456, etc.
    const jiraKeyRegex = /([A-Z]{2,}-\d+)/g;
    const matches = branchName.match(jiraKeyRegex);
    
    if (!matches || matches.length === 0) {
      console.log(`No Jira key found in branch: ${branchName}`);
      return $.flow.exit('No Jira ticket key found in branch name');
    }
    
    // Take the first match if multiple keys exist
    const ticketKey = matches[0];
    
    return {
      ticket_key: ticketKey,
      pr_title: prTitle,
      pr_url: prUrl,
      author: author,
      branch_name: branchName,
      comment: `PR opened by ${author}: ${prTitle} - ${prUrl}`
    };
  }
});

Code Step > Editor

Write ticket key extraction logic

In the code editor, write logic to parse the branch name and extract Jira ticket keys. The branch name comes from steps.trigger.event.pull_request.head.ref. Use a regex pattern to match your Jira project key format. If no ticket key is found, the workflow should exit early to avoid unnecessary API calls.

1. 1Clear the default code in the editor
2. 2Write regex logic to extract ticket keys
3. 3Add validation to check if a key was found
4. 4Return the extracted key or exit if none found

Workflow Builder > Add Step > Jira

Add Jira API step

Add another step and search for Jira in the app directory. Choose 'Update Issue' as the action since you're changing the ticket status. You'll need to connect your Jira instance using your email and an API token. The step configuration will show fields for issue key, transition ID, and other update parameters.

1. 1Click '+ Add a Step' below the code step
2. 2Search for 'Jira' and select it
3. 3Choose 'Update Issue' from the actions
4. 4Click 'Connect Account' to add Jira credentials

Jira Step > Account Connection

Configure Jira connection

Enter your Jira site URL without trailing slash, your email address, and an API token. Get the API token from your Atlassian account settings under Security > API tokens. Test the connection to make sure Pipedream can reach your Jira instance. Some corporate firewalls block external webhook calls.

1. 1Enter your Jira URL (e.g., company.atlassian.net)
2. 2Enter your Jira email address
3. 3Paste your API token from Atlassian account
4. 4Click 'Test' to verify the connection

Jira Step > Issue Key Field

Map issue key from code step

In the Issue Key field, reference the output from your code step. Click the + button next to the field to see available data. Navigate to your code step output and select the ticket key variable. This creates a dynamic reference that uses the extracted key for each PR.

1. 1Click the '+' button next to Issue Key field
2. 2Expand the code step output section
3. 3Select the ticket key variable you returned
4. 4Verify the reference shows in the field

This code extracts Jira ticket keys from branch names and handles multiple project prefixes. Paste this in your Node.js code step to replace the default template.

export default defineComponent({
  async run({ steps, $ }) {
    const branchName = steps.trigger.event.pull_request.head.ref;

export default defineComponent({
  async run({ steps, $ }) {
    const branchName = steps.trigger.event.pull_request.head.ref;
    const prTitle = steps.trigger.event.pull_request.title;
    const prUrl = steps.trigger.event.pull_request.html_url;
    const author = steps.trigger.event.pull_request.user.login;
    
    // Match Jira ticket patterns like PROJ-123, AUTH-456, etc.
    const jiraKeyRegex = /([A-Z]{2,}-\d+)/g;
    const matches = branchName.match(jiraKeyRegex);
    
    if (!matches || matches.length === 0) {
      console.log(`No Jira key found in branch: ${branchName}`);
      return $.flow.exit('No Jira ticket key found in branch name');
    }
    
    // Take the first match if multiple keys exist
    const ticketKey = matches[0];
    
    return {
      ticket_key: ticketKey,
      pr_title: prTitle,
      pr_url: prUrl,
      author: author,
      branch_name: branchName,
      comment: `PR opened by ${author}: ${prTitle} - ${prUrl}`
    };
  }
});

Jira Step > Transition Configuration

Set transition to In Review

Find the transition ID for moving tickets to In Review status. Go to your Jira project settings > Workflows > View workflow to see available transitions. Each transition has a numeric ID. Common IDs are 21 for In Review or 31 for In Progress, but these vary by Jira setup.

1. 1Open your Jira project in another tab
2. 2Go to Project Settings > Workflows
3. 3Note the transition ID for 'In Review'
4. 4Enter this ID in the Transition field

Workflow Builder > Test Button

Test the complete workflow

Click Test at the top of the workflow to run it with sample data. Create a test branch with a Jira ticket key in the name, then open a PR. Check that the workflow triggers, extracts the key correctly, and updates the Jira ticket status. Review the execution log for any errors.

1. 1Click 'Test' in the workflow header
2. 2Create a test PR with ticket key in branch name
3. 3Watch the workflow execution in real-time
4. 4Check your Jira ticket for status change

Workflow Builder > Deploy Button

Deploy workflow

Once testing works, click Deploy to activate the workflow for all future PRs. The webhook will now process every PR opened in your connected repository. You can monitor execution history in the workflow dashboard and see success/failure rates over time.

1. 1Click 'Deploy' in the workflow header
2. 2Confirm deployment in the modal dialog
3. 3Check that status changes to 'Active'
4. 4Monitor the execution log for live events