Here is the endpoint I'm hitting:
https://<our_domain>>.atlassian.net/rest/api/3/project/search?expand=description,lead&maxResults=1
Hello @ben.wilen
Welcome to the Atlassian community.
It appears that the endpoint returns only non-archived, non-deleted projects by default, and since they are live projects it appears to exclude the archived-related fields.
You can search the archived projects by adding status=archived to the parameters.
Hi @ben.wilen
Can you check if this works?
/rest/api/3/project?includeArchived=true
The property for that can be found here:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-get
Although the project is deprecated, now we need to use this project paginated:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-search-get
Regards
Thank you for the quick response @Aaron Pavez _ServiceRocket_ !
"/rest/api/3/project?includeArchived=true" returns the archive field, and "/rest/api/3/project" also returns the archive field.
Can you clarify "Although the project is deprecated, now we need to use this project paginated:"...does that mean the recommended method is to use the deprecated endpoint or is there a way to use the "project/search" endpoint and still get the archive field?
Thank you! To keep the api calls symmetrical is there a "status=..." for active projects? "status=active" did not work.
Adding to this...
The ?includeArchived=true parameter noted by @Aaron Pavez _ServiceRocket_ does not work with the /rest/v3/project/search endpoint.
@Trudy P Claspill Yep, seeing that and thank you for pointing that out! Just to make sure I'm not missing anything, are there any other statuses besides "active" that can be passed to the URL?
It looks like you're new here. Sign in or register to get started.