Skip to content
ClickRuntime

Connect GitHub to Jira

Many companies plan in Jira and write code in GitHub, and the two drift apart. Connecting them turns GitHub bug reports into Jira tickets, opens tickets for real security risks in your dependencies, and gives the team one morning summary of both.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with GitHub and Jira

Bug tickets, security tickets and a daily digest, keeping GitHub and Jira in step. These are ready-made starting points. Anything else you can describe works too.
On a scheduleAI

Post a daily digest of Jira and GitHub activity

Every weekday morning Slack shows which Jira tickets moved and which pull requests were opened or merged, with a short summary.

See how it works
The moment it happensAI

Turn GitHub bug reports into Jira tickets

When a bug is reported on GitHub, a Jira ticket is created with an AI summary and priority, and the GitHub issue gets a comment with the Jira key.

See how it works
Every 6 hours

Open Jira tickets for exploited vulnerabilities in your dependencies

Every 6 hours your repositories' dependencies are checked against public vulnerability data, and each new known vulnerability gets one Jira ticket.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with GitHub and Jira, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any GitHub and Jira automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between GitHub and Jira in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Each morning, list open GitHub PRs whose Jira ticket is already Done or missing, and post the list as a comment on our team's tracking ticket.

When a GitHub issue gets the label customer, create a Jira bug only if AI judges it a real defect, and set the priority from the number of reactions.

Use cases

Why people connect GitHub and Jira

How the two apps work together

  • GitHub webhooks send pull request and issue events to a ClickRuntime trigger link.
  • The script reads the Jira key from the branch or PR title and transitions, comments on or creates the Jira issue.
  • Jira webhooks or a check every few minutes can carry Jira changes back to GitHub, such as closing an issue.

  • Jira status follows pull requests

    Teams that plan in Jira and code in GitHub move a ticket to In Review when a PR with its key opens and to Done when it merges. Nobody has to update the board by hand.

  • Open source issues into an internal backlog

    Companies with public repositories copy labeled GitHub issues into a Jira project for planning. The Jira ticket keeps a link to the public issue.

  • Release notes from Jira and GitHub together

    Release managers combine merged PRs with the fix versions of their Jira tickets to write notes. The result lists customer-facing changes by ticket.

  • Catch pull requests without a ticket

    Engineering managers who require a Jira key in every PR title get a list of PRs that are missing one. It keeps audit and time tracking intact.

More apps

GitHub, Jira and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Merged PRs move Jira and notify Slack

When a PR with a Jira key merges, move the ticket to Done and post the ticket and PR link in #releases.

Release notes page in Confluence

When we publish a GitHub release, write a Confluence page listing the Jira tickets fixed, using the keys from the merged PR titles.

Sentry errors to Jira with GitHub fix link

Create a Jira bug for new Sentry errors, and when a GitHub PR referencing that bug merges, comment the PR link on the ticket.

Setup

Connect GitHub and Jira once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

GitHub

Developer / Source control

  1. In GitHub, open your profile picture, then Settings, Developer settings, Personal access tokens, Fine-grained tokens, and choose Generate new token.
  2. Give it a name and an expiration, and choose the resource owner (you or your organization).
  3. Under repository access, pick only the repos the automation needs, then set the minimum permissions, such as Issues, Pull requests or Contents.
  4. Generate the token and copy it.
  5. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for GitHub.

Jira

Project management / Issue tracking

  1. Go to id.atlassian.com/manage-profile/security/api-tokens and choose Create API token. Atlassian sends a code to your email to confirm.
  2. Name the token, choose an expiry of 1 to 365 days, create it and copy it straight away. It can't be shown again.
  3. Note your site address, such as yoursite.atlassian.net, and the email of the Atlassian account that created the token.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the email, token and site for Jira.

FAQ

Questions about connecting GitHub and Jira

How does ClickRuntime connect to Jira?
Through your Atlassian account, connected in your ClickRuntime dashboard. Tickets are created by that account in the projects it can access.
Which Jira project do tickets go to?
The one you name, such as ENG or SEC. Different automations can use different projects and issue types.
Does it link the Jira ticket and the GitHub issue?
Yes, where it creates both sides. The Jira ticket includes the GitHub link, and a comment on the GitHub issue gives the Jira key.
Does it work with Jira Server or Data Center?
These automations use Jira Cloud. Self-hosted Jira can work with a personal access token if it is reachable over HTTPS.
Does it work with Jira Cloud?
Yes. ClickRuntime connects to Jira Cloud through your own connection, and the script uses the Jira REST API.
Can it move tickets through my own workflow?
Yes. The script uses the transitions available in your Jira workflow, so you name the status it should move to.
Is the sync two-way?
It can be. Each direction is part of the script, so you decide which changes in GitHub update Jira and which Jira changes update GitHub.

Related pages

Keep exploring

Tell your assistant what GitHub and Jira should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude