500 Error when trying to move sub-tasks to another issuetype and project

[Karl Samson]

Hi All, I'm trying to do a Bulk move a number of sub-tasks, in different statuses, to a different issuetype in a different project. I have managed to move one of them, but if I try all or even two of them, I receive a 500 error?

We have recently performed a full Re-Index.

[Sharumathy Krishnan · Accepted solution]

Hi @Karl Samson 

I came across similar issue in the Atlassian community, kindly take a look at it - https://community.atlassian.com/t5/Jira-Software-questions/Error-500-when-converting-subtask-to-issue/qaq-p/1278198 

Also, if you are trying to convert the subtask to Next-gen project. There is a workaround provided in https://jira.atlassian.com/browse/JSWCLOUD-18442 

If these doesn't help you, kindly raise a request with Atlassian support - https://support.atlassian.com/ 

Thanks,

Sharu

[Karl Samson]

Hi Sharu, I've actually now managed to move all the 'Completed' status sub-tasks across. However, three remain and keep getting the 500 error. I've checked the Permissions in both projects concerned, and I am able to Schedule, Transition and Move. One of the Sub-Tasks is in 'New', the other two in 'In Progress'.

I will raise a support ticket with Atlassian.

Thanks anyway.