Hi,
I am working on a solution that needs to move items between projects, for which we are happy to be able to use the new /rest/api/3/bulk/issues/move endpoint.
Now a concern came up with that currently this endpoint does not throw an error in case an item that is marked to be moved is archived. We would like to prevent a solution where we have to refetch every issue to see if it’s archived, since we already ran into some rate limiting on other parts of our application.
This is also inconsistent with the jira cloud web ui where the move operation is not available in the issue when it’s archived; also if you manually build the url via secure/MoveIssue!default.jspa?id=<INTERNAL_ID> you will land on an access denied/operation not allowed page
Optimally this would be validated when creating the task via the bulk/issues/move. could also be an additional property in the body that allows/disallows operations on archived issues.
cheers