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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

REST API get all issues of version? Edited

Hello all,

I'm trying to find the correct endpoint where I can make a xttp request and get back all issues specifying versionID orKey.

I can just get a count of resolved, unresolvet, etc.

I'd be surprised if Its impossible to get a JSON with all issues of a version

Is thisavailable?

 

Thanks

1 answer

1 accepted

0 votes
Answer accepted
Warren Community Leader Nov 13, 2019

Hi @Adria_Alonso 

I use the cloud version, but looking at the API doc for server, this should be possible.

Run a generic search using /rest/api/2/search and pass in a JQL like fixVersion=ReleaseXX 

Yes, thank you, just got into that by following this thread

https://community.atlassian.com/t5/Jira-questions/How-to-get-all-issues-of-a-project-using-Rest-API/qaq-p/832316

I was changing project for version, but its expecting fixVersion.

Awesome!!

Thanks

@Warren 

Is it necessary to use POST to get more than 50 issues without modifying the hard coded 50 issues per jira search?

Thank you

Warren Community Leader Nov 18, 2019

Hi @Adria_Alonso 

I'm not sure what you're asking, POST is for changing data in Jira, you're using GET to read the data.

You should be able to add &maxResults=100 but you cannot retrieve more than 100 in one call, so your call would look something like :

/rest/api/2/search?jql=fixVersion=ReleaseXX&maxResults=100

If you expect or have more than 100 results, you will need to use multiple calls, where your second call would add &startAt=100 and the 3rd call would change it to &startAt=200

Thank you, Certainly POST is for sending not retrieving, just had a hard day.. (the parameter wasnt working and i thought maybe i needed to send it in post with a json in body)

Thank you for your answer, I understand for the 100, due to the fact that i can be a lot of time to deliver the Json and end in a timeout call. I think i'll stick with the maxresults at 100 and then the startat and use some pagination.

Thank you again,

Suggest an answer

Log in or Sign up to answer
TAGS

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