Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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 server issues in search results are missing issuelinks


Running Jira Server 8.5.12

We are using the Jira search API `rest/api/2/search` to get details of a task including `issuelinks` but it always returns an empty list of that field even though there are issues linked to the task. An example of the request is below

curl --request POST \
--url SERVER_URL/rest/api/2/search \
--header 'Accept: application/json' \
--header 'Authorization: xxxx' \
--header 'Content-Type: application/json' \
--data '{
"jql": "issue = ISSUE-1",
"fields": [
"expand": ["changelog"],
"maxResults": 100


Also tried using `"fields": [*all]` with the same result.


What is kinda surprising is that when I use the issue endpoint `/rest/api/2/issue/{issueIdOrKey}`, the issue links are present in the response.

Wondering what could be causing that behavior if anyone has encountered that.



1 answer

0 votes

I generally use the Jira Python library and I see the same thing. The search returns issue and then I have to call that second issue REST resource to get the issue links

I looked for an expand parameter value to do this but didn't see one

Yeah, it is very weird. Doing the extra call isn't really a great option for us since we are querying for many issues at the same time so don't want to overload the server.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events