No option to skip/fail on /rest/api/3/bulk/issues/move if issues are archieved

[Paul Haller]

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 this endpoint does not throw an error in case a 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 inconsistent with the jiracloud web ui where the move operation is not available in the issue when its archived; also if you manually build the url 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

[Trudy Claspill]

Hello @Paul Haller 

Welcome to the Atlassian community.

You are correct that does not appear to be a feature of the API currently. If you would like to get that suggestion directly to Atlassian I suggest you use the Help > Feedback option available directly in Atlassian. Since this is a user community, it is not the best method to submit a suggestion and ensure that Atlassian sees it.

The API requires as input an array of the issues that you want to move. As a workaround you could precheck that list to ensure that it does not include archived issues.