I’m working with Jira cloud and need to extract issue information along with all related metadata. The main challenge I’m facing is getting the GitHub integration details that show up in the Development section of issues. This includes stuff like pull requests, commits, and branch information that gets linked from our GitHub repos.
I’ve been trying to pull this data through Jira’s REST API but having no luck. Tested both v2 and v3 endpoints but none of them seem to include the actual GitHub repository links in the response. The development section just doesn’t appear in the JSON output.
Does anyone know if there’s a specific API endpoint or method to access this GitHub integration data? Maybe there’s a different approach or workaround that I’m missing?
GitHub integration data lives in a separate service - the Development Information API. Most devs miss this since it’s not in the standard Jira REST docs. You need to hit /rest/dev-status/latest/issue/details instead of regular issue endpoints. Your API token needs development tools access, not just issue management permissions. The response structure is completely different from normal issue data. GitHub info comes back as nested objects under repository details - you’ll dig through multiple levels to get PR numbers, commit hashes, and branch names. One gotcha: this endpoint only returns data when the GitHub integration actually found linked work. Empty responses don’t mean it’s broken - just means no GitHub activity for that issue.
hit the /rest/dev-status/1.0/issue/detail endpoint with your issue key. it works for GitHub integrations - just ensure you have the right auth headers. not really documented, but I’ve pulled PR and commit data from linked repos with it before.
Been dealing with this exact headache for years. GitHub data in Jira’s Development section comes through webhooks but gets stored where you can’t reach it with normal REST calls.
Jira deliberately walls this off since it’s managed by the GitHub app, not core Jira. You’d have to mess with Atlassian Connect or hunt down undocumented APIs - both options suck and break constantly.
Skip the API wrestling. I always fix this with automation instead. Build workflows that grab the data as it moves between systems and store it however you want.
Set up automated processes watching both Jira issues and GitHub events, then mash that data into whatever format you need for reports or analysis. Way cleaner than reverse engineering their proprietary endpoints.
You get full control over data structure and won’t break when Atlassian changes things. Plus you can toss in other data sources later without starting over.
Check out Latenode for building these integrations. It handles API complexity so you can focus on getting your actual data: https://latenode.com