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: 

Content api output

Scott Aquilina
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 15, 2022

I have been working on some automation to get the attachment url from the content field in the API and everything was working. However I started getting 303 errors.

When I looked into the API the URL was completely different.

 

When it was working:

Now:
Not sure what happened, but I have tested in 3 environments and I am getting the same result.
Any help would be appreciated.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Pramodh M
Community Champion
January 15, 2022

Hi @Scott Aquilina 

Welcome to the Community!!

To get the attachment details,

First, get the attachment id from the GET issue request

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get

Now you will have the attachment id to make the GET request on attachment

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-attachment-content-id-get

Thanks,
Pramodh

Scott Aquilina
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 15, 2022

Thanks for this, seems to have fixed the issue

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events