You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|_**issueKey**_|_String_. Optional.<br><br>This is the Jira Issue Key – a concatenation of Project key and Issue number. It must contain a dash ('-'). The _**issueKey**_ must be valid and existent.<br><br>For example: `TEST-435`. |
96
+
97
+
### Response
98
+
99
+
It includes branches whose name is associated with the issue. The result will show the branches on which commits exist in the specified Jira issue. It's a set of branches to which the commits are bound to the issue they are associated with. They can be viewed in the the Git Commits tab.
### I made the correct request but I don't see the expected branches in the results?
147
+
148
+
If the issue displays these branches while the request does not, the likely explanation is that, the request is being executed by a user who lacks sufficient permissions to access the repository. (See the yellow infobox above.)
149
+
150
+
For a quick check, it is possible to omit the issue key in the request.
151
+
152
+
It will look like this: `https://jira.your-org.com/rest/gitplugin/1.0/issues/branches`
153
+
154
+
When a user is granted specific permissions, they will receive a json response that shows various branches.
155
+
63
156
64
157
<hr>
65
158
66
159
67
-
**[« Back to REST API index](/git-integration-for-jira-data-center/rest-api-gij-self-managed)**
160
+
161
+
**[« Back to: REST API index](/git-integration-for-jira-data-center/rest-api-gij-self-managed)**
0 commit comments