nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA API errors with Gone/410 : This API has been deprecated and is no longer available

Paul Lambert1

We have integration to JIRA to put a list of assets into JIRA. Then in JIRA service management, we use the JIRA asset panel with a https call into our web app to show details of each asset in the asset panel.

However its stopped working with error message:

(410) Gone. HTTP 410 This API has been deprecated and is no longer available.

The API endpoint is:

https /your jira domain/rest/assetapi/asset/bulk

The JIRA documentation here https://developer.atlassian.com/cloud/assetsapi/rest/api-group-assets/#api-group-assets does not indicate that these methods are deprecated.

(I posted this on reddit also)

What seems strange is that the asset list and the asset panel are still working, just that you can't now push more assets into JIRA because the /bulk endpoint no longer exists. I thought if they were taking away the ability to store assets, then all of it would be broken. This has affected several customers and our test instance. Our test instance is not premium, I don't know what our customers have.

Accepted answers

Kai Krause_xx7uj7

Hi,

when you look here About External Assets Platform the External Assets Platform is shutdown on 31.12.2024.

Support and Guziddance you finde here:

Shutdown Notice: Update on deprecation of the External Assets Platform - Announcements - The Atlassian Developer Community

BR

Kai

All comments

Kai Krause_xx7uj7

Hi,

when you look here About External Assets Platform the External Assets Platform is shutdown on 31.12.2024.

Support and Guziddance you finde here:

Shutdown Notice: Update on deprecation of the External Assets Platform - Announcements - The Atlassian Developer Community

BR

Kai

Paul Lambert1

Ah what a pain, in the midst of all the junk we get from atlassian we did not pick that up, and now we have customers in a mess. This does appear to be a terrible way to treat your customers, i.e. why not continue to allow it to work for a while, but I guess thats a market gorilla for you

Dorothea Linneweber

Hi @Paul Lambert1 , thank you for the valued feedback. We will ensure that in the future all subpages are updated, not just the parent page.

Please note that in addition to community articles, and in-UI messaging, we also sent emails to all admins of impacted sites notifying and reminding of the gradual shutdown that is occurring since 31.12.2024, so hopefully most customers are aware this is happening.

Over the coming weeks the field will be removed altogether, however the intention was to start with the ability to add new/additional assets in order to allow for easier data recovery. We understand this could be misleading so have again noted this and will pass it on to the relevant teams.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management