Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Error while moving sub-bug to sub-task

David Shahbazyan
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 Champions.
July 6, 2026

I want to move an issue from Sub-bug to Sub-task under the parent Story, but I am getting the following error:

image (1).png

I already checked the Issue Type Scheme configuration, and both issue types seem to be available.

I also want to understand whether this issue is related to required fields. From what I know, if the problem is related to fields, Jira usually shows those fields in the next step during the move operation.

Could someone please help me understand why I am getting this error and what configuration I should check to move a Sub-bug to a Sub-task successfully?

1 answer

0 votes
Gabriela
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 Champions.
July 6, 2026

Hi @David Shahbazyan, it's not the required fields, those only show up on the later update-fields step. On Data Center the Move Sub-Task wizard validates your target type against the Default Issue Type Scheme, not the project scheme you already checked, and Jira Software's default scheme doesn't include Sub-task. That's exactly why step 2 throws "The issue type selected is invalid." Go to Settings > Issues > Issue type schemes, edit the Default Issue Type Scheme, drag Sub-task into it and save, then rerun the move. Background here: Atlassian KB.

David Shahbazyan
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 Champions.
July 6, 2026

Dear @Gabriela , in my Default Issue Type Scheme there are all my available issue types. I think this is a bug with my current version.

Suggest an answer

Log in or Sign up to answer