The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Not returning fix version in API call

Mark Davies
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 28, 2022

Using the following URL: https://ctl.atlassian.net/rest/api/3/search?jql=filter=66847

to return the results (which it does correctly), the filter itself is:

issuetype in ("Portfolio Epic", Capability, "Epic (Feature)", Story) AND issueKey in portfolioChildIssuesOf(ABC-123) AND status not in (Done) ORDER BY key

Yet, when I look at the result in JSON - it shows a "list" but all fix versions are empty. How can I resolve that?

 

fields 
fixVersions[]
14 
fields 
fixVersions 
15 
fields 
fixVersions 
16 
fields 
fixVersions 
17 
fields 
fixVersions 
18 
fields 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 28, 2022

Hi @Mark Davies 

I just tried this for my own filter and it worked for me.  Some things to check are:

  • Run the JQL manually in advanced search and confirm it works, and confirm the returned issues actually have fixVersion values
  • Run that same REST API call in a browser to confirm it works, and look for the fixVersions.  If it works, it may be how you are consuming the response.

Kind regards,
Bill