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; } } }

Can not delete objects with inboundReferences by API REST delete method

Daniel Canizalez

Hi we have a problem when try to delete object with inbound references

we use DELETE method: DELETE:XXXX/rest/insight/1.0/object/436352

but it responds with HTTP 500 because it object have a inbound reference, there is a way to force delete

Accepted answers

Fabio Racobaldo _Catworkx_

Hi @Daniel Canizalez ,

are u sure that inbound reference is the problem? Error 500 should be an Internal Server error.

Please let us know about error reported at the log file level.

Btw, my suggestion is to try to reindex your objects first :

Indexing

To open indexing configuration, select Indexing Insight.

Re-index
A re-index means that all objects will stay in the index during the process, and Insight will index them again. You can search for objects during the process.

Hope this helps,

Fabio

All comments

Fabio Racobaldo _Catworkx_

Hi @Daniel Canizalez ,

are u sure that inbound reference is the problem? Error 500 should be an Internal Server error.

Please let us know about error reported at the log file level.

Btw, my suggestion is to try to reindex your objects first :

Indexing

To open indexing configuration, select Indexing Insight.

Re-index
A re-index means that all objects will stay in the index during the process, and Insight will index them again. You can search for objects during the process.

Hope this helps,

Fabio

Daniel Canizalez

Hi Fabio, we are sure because we try with another object without inbound references and it is delete without problems

we try to put directly the api users as Object Type Manager but the same error.

we delete directly in the interface and it delete even if it has inbound references but via API we cant

Fabio Racobaldo _Catworkx_

it's strange because, usually, REST API allows you to perfom the same operation as per user interaction with the UI (with the same checks)

Daniel Canizalez

Thanks Fabio, now we re check the user role and has less privileges

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server