Unable to move ticket or publish workflow / Internal Server Error

Dany Jupille
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 3, 2025

Hi,

I am trying to do some cleanup on our Jira software project and I'm currently blocked on an issue where I have tickets in an inconsistent state. Those tickets are not visible in the backlog, have no state and are still assigned to an obsolete ticket type.

When I try to move them or convert them as sub-task in order to "reset" their fields to the new ones, I get an Internal Server Error.

Log example with a move error: ee6f097c-ba10-4e9f-9775-3adbb26a80ee

I thought that maybe making a transient workflow and workflow scheme in which I would include all previous states and ticket types I could workaround this... but I get an Internal Server Error as well when I try to publish the said workflow!

Log example of the publish error: 70ab2715-be2c-4131-be22-e1166d5c4ac7

I am kinda blocked now as I don't have access to the logs in Jira Cloud.

Any help would be appreciated; thanks in advance.

Best regards

1 answer

0 votes
Pasam Venkateshwarrao
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2025

Hi @Dany Jupille 

welcome to the community,First can you check the Board settings whether you are having access to that filter or not.

while convert to subtask you need to select parent task and also check the permissions whether "Move" issue permission is there or not

Dany Jupille
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 3, 2025

Hi @Pasam Venkateshwarrao and thank you for your time.

The rights of my user account on the project cannot be changed as it is the free plan for Jira.

But it seems that I do have the rights as I was able to fix some tickets.
That is the weird part: some tickets have the issue, but others not.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events