Re: Roundup rest API

Using the DELETE command and having ADMIN role assigned makes it working well.
The "deleted" issue will be set to retire and is excluded from search

Thanks
Norbert

-----Ursprüngliche Nachricht-----
Von: [email protected] <[email protected]> 
Gesendet: Donnerstag, 13. Juli 2023 15:23
An: SCHLEMMER Norbert <[email protected]>
Cc: [email protected]
Betreff: Re: AW: [Roundup-users] Roundup rest API

*EXTERNAL source*


In message <[email protected]>,
SCHLEMMER Norbert writes:
>Hello John
>
>Want to add the "delete / remove" issue function, but how ?
>
>The #patch command with "@op=remove" will be executed with return code 
>"200 OK"

Just a note, using the DELETE verb will do the same and is arguably easier to use.  @op=remove was added to match @op=restore since there is no HTTP verb that matches the restore function.

>but the issue is still visible and part of the search result

The issue will be retreivable if you use its full rest path
.../rest/data/issue/23 for example. There have been discussions about returning a 404 or hiding a retired item. But we haven't had any concrete ideas on impementing it. This can be a problem for users and GDPR. https://wiki.roundup-tracker.org/RemovingUsers may be helpful.

It should not be listed in an index view. E.G. .../rest/data/issue should not show the retired issue.

What type of search are you doing, what URL? Also what roles does the searching user have?

Have a great day.
--
                                -- rouilj John Rouillard ===========================================================================
My employers don't acknowledge my existence much less my opinions.