Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA REST API to get list of branches related to a issue


How do i get the list of branches related to a issue using JIRA REST API.  i tried using the rest/api/2/issue/. but it doesn't return any information related to the branches.

Any Help would be appreciated.

2 answers

Hi Visigan,

I've been having a look and wasn't able to find an official REST api but when I looked at how Jira itself was getting the data (pull requests but also branches) I've found the following call:

GET /rest/dev-status/1.0/issue/detail?issueId=<ISSUEID>&applicationType=bitbucket&dataType=pullrequest

Unfortunately the request requires the issue ID and not the issue Key. So you'll need to retrieve the issue ID using the Jira Issue REST api first (/rest/api/latest/issue/<ISSUEKEY>) first.

Please do keep in mind this is not an official API which could be changed between Jira versions without any notification.



Thanks, Maarteen

it works for me, but there is an issue. The JSON returns all the commits but only the part of the files committed. if i commit more than 5 files on a single commit, then only the first 5 files are listed in the JSON. any ways to get the full list of files?

I’m afraid that using the api of either Bitbucket or github in this case will be the only option.



I tried them too, /rest/api/1.0/projects/{Project}/repos/{Repo}/commits/{commit id} is not returning any information about the files. do you aware of any other bitbucket API which gives me the list of files related to a commit.

I am receiving response as 200 but no details are pulled

{    "errors": [],    "detail": []}

@Yasashree, use "stash" instead of "bitbucket.  The following worked for me:

GET /rest/dev-status/1.0/issue/detail?issueId=<ISSUEID>&applicationType=stash&dataType=pullrequest

what is the applicationType for Azure ?

it should be `details` instead of `detail` in the URL.

It would be something like this:



where ISSUE_ID is the ID, not the key

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you