How to sync GitHub issues to Jira with Power Automate

My flows > + New flow > Automated cloud flow

Create new automated cloud flow

Go to make.powerautomate.com and sign in with your Microsoft account. Click My flows in the left sidebar, then + New flow. Select Automated cloud flow from the dropdown. Name your flow 'GitHub Issue to Jira Sync' and leave the trigger selection for the next step.

1. 1Click My flows in the left sidebar
2. 2Click + New flow button
3. 3Select Automated cloud flow
4. 4Enter flow name: GitHub Issue to Jira Sync
5. 5Click Create

Flow designer > Choose your flow's trigger

Add GitHub webhook trigger

In the trigger step, search for 'GitHub' and select the GitHub connector. Choose 'When an issue is opened' trigger. If you haven't connected GitHub before, you'll see a sign-in prompt. Use a GitHub account with admin access to your target repository.

1. 1Click in the trigger search box
2. 2Type 'GitHub' and select the GitHub connector
3. 3Select 'When an issue is opened' trigger
4. 4Sign in to GitHub when prompted
5. 5Authorize Power Automate access

GitHub trigger > Repository selection

Configure repository selection

Select your GitHub repository from the Repository dropdown. Power Automate will automatically create a webhook in your repository pointing to Microsoft's servers. The webhook fires immediately when new issues are created, not on a polling schedule.

1. 1Click the Repository dropdown
2. 2Select your target repository
3. 3Leave other fields at default values

Flow designer > + New step > Choose an action

Add Jira connection

Click + New step below the GitHub trigger. Search for 'Jira' and select the Jira connector. Choose 'Create issue' action. When prompted to sign in, use your Atlassian account credentials. Power Automate supports both Jira Cloud and Jira Server instances.

1. 1Click + New step
2. 2Search for 'Jira'
3. 3Select Jira connector
4. 4Choose 'Create issue' action
5. 5Sign in to Atlassian when prompted

Jira Create issue > Project and Issue Type

Configure Jira project and issue type

Select your target Jira project from the Project dropdown. Choose 'Task' or 'Bug' from the Issue Type dropdown based on your workflow needs. These dropdowns populate dynamically from your Jira instance, so you'll only see projects where you have create permissions.

1. 1Select target project from Project dropdown
2. 2Choose appropriate Issue Type (Task/Bug/Story)
3. 3Wait for additional fields to load

Jira Create issue > Summary and Description fields

Map issue title and description

Click in the Summary field and select 'Title' from the GitHub dynamic content panel. For Description, click the field and select 'Body' from GitHub content. The dynamic content panel shows all available fields from the GitHub webhook payload including issue metadata.

1. 1Click in Summary field
2. 2Select 'Title' from GitHub dynamic content
3. 3Click in Description field
4. 4Select 'Body' from GitHub dynamic content

Add this expression in a Compose action between GitHub and Jira to clean up markdown formatting and add GitHub context to the description.

concat(
  'Original GitHub Issue: ', triggerOutputs()?['body/html_url'], 
  char(10), char(10),

concat(
  'Original GitHub Issue: ', triggerOutputs()?['body/html_url'], 
  char(10), char(10),
  replace(
    replace(
      replace(
        triggerOutputs()?['body/body'],
        '**', '*'
      ),
      '', '{code}'
    ),
    '##', 'h2.'
  )
)

Jira Create issue > Assignee field

Map assignee field

Scroll to the Assignee field in the Jira action. Click the field and look for 'Assignee Login' in the GitHub dynamic content. This maps the GitHub assignee username to Jira. Note that the GitHub username must match exactly with a Jira user account for this mapping to work.

1. 1Scroll down to find Assignee field
2. 2Click in the Assignee field
3. 3Select 'Assignee Login' from GitHub content

Jira Create issue > Labels or Custom fields

Handle labels mapping

For labels, click in a Jira Labels field if available, or use a custom field. Select 'Labels' from GitHub dynamic content. GitHub sends labels as an array, but Power Automate handles the conversion automatically. Jira will create new labels if they don't exist in your project.

1. 1Look for Labels field or custom label field
2. 2Click in the labels field
3. 3Select 'Labels' from GitHub dynamic content

Jira action > ... menu > Settings > Configure run after

Add error handling

Click the three dots menu on the Jira action and select Settings. Turn on Configure run after and check 'is successful' and 'has failed'. This ensures the flow continues even if Jira ticket creation fails, preventing GitHub webhook timeouts.

1. 1Click three dots on Jira Create issue action
2. 2Select Settings
3. 3Toggle Configure run after to On
4. 4Check both 'is successful' and 'has failed'

Flow designer > Save > Run history

Test the workflow

Save your flow by clicking Save in the top toolbar. Create a test issue in your configured GitHub repository with a title, description, assignee, and labels. Check the flow run history in Power Automate to verify the webhook triggered and the Jira ticket was created successfully.

1. 1Click Save in the top toolbar
2. 2Go to your GitHub repository
3. 3Create a new issue with all fields populated
4. 4Return to Power Automate and check Run history
5. 5Verify the flow succeeded and check Jira for the new ticket