AI Launch Profile

GitHub Copilot for Jira reaches GA: June 25, 2026 launch record

GitHub Copilot for Jira reached general availability, adding real-time Copilot cloud-agent progress inside Jira, post-session steering and simplified onboarding for connected GitHub repositories.

Read official source Tool profile

At a glance

Launch Snapshot

Company: GitHub
Launch date: June 25, 2026
Launch type: Not classified
Category: AI Agents, AI Coding Tools, AI Productivity Tools
Audience: AI Platform Teams, Developers, Engineering Teams, Enterprises
Pricing: The integration follows paid GitHub Copilot access and eligible Jira Cloud configuration. Cloud-agent work consumes AI credits and GitHub Actions minutes; no separate integration price is listed.
Free plan: No
API: Not publicly confirmed
Open weights/source: No

Launch Context

Use these links to move from this record into the broader Launch Intelligence database.

Launch Intelligence hub Today's launches This week's launches More: AI Agents More: AI Coding Tools More: AI Productivity Tools More: AI Platform Teams More: Developers More: Engineering Teams More: Enterprises

Verification & Sources

Evidence state: Recheck due
Source links: 5
Freshness: Needs recheck: checked July 31, 2026
Last updated: July 31, 2026

What this evidence state means

Definition: The claim was previously checked, but its review window expired or a material change may have invalidated it.
Required provenance: The prior evidence and check date are retained, together with the expiry or change signal that triggered recheck.
Owner: Kingy freshness queue owner and assigned editorial reviewer
Freshness rule: This is already outside its freshness rule. It must not be presented as current until reviewed against current evidence.
Disputes and corrections: Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.

Key source checks

Official site Official announcement Pricing Source 3 Source 4

Suggest a correction

Kingy AI Take

The GA release closes useful workflow gaps by returning agent progress and follow-up control to Jira. The integration also moves ticket context into a coding workflow and depends on two app installations, repository permissions, Rovo and SSO state. Kingy did not install it, so teams should test context exposure, duplicate-session behavior, revocation and review controls on a limited repository.

Who it is for

Developers, engineering teams, AI platform teams and enterprises using Jira Cloud and paid GitHub Copilot with governed app installation, repository access and pull-request review.

What feels promising

Real-time progress, Jira-native task initiation and supported follow-up steering can reduce context switching while leaving code changes inside GitHub review.

What feels unproven

Kingy did not measure task success, context fidelity, duplicate pull requests, SSO edge cases, permission revocation, Actions consumption, AI credits or behavior across custom agents and models.

Source list

Sources

Official site docs.github.com Source github.blog Source docs.github.com Source github.com Source docs.github.com