Error while moving sub-bug to sub-task

[David Shahbazyan]

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

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?

[Gabriela - LeanZero]

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]

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

[Gabriela - LeanZero]

You're right — if your Default scheme already has Sub-task, my first suggestion doesn't apply. This is a real Data Center bug, not just your version: the Move Sub-Task wizard validates the target type against whatever the database has flagged as the default issue-type scheme, not your project's scheme (tracked as JSWSERVER-20464, still open). When the visible Default scheme looks complete but the move still fails, the DB usually has the wrong scheme set as default. Quick check: run SELECT id FROM configurationcontext WHERE customfield='issuetype' AND project IS NULL — it should return 10000; anything else confirms it, and the fix + SQL is here: https://support.atlassian.com/jira/kb/issue-type-invalid-error-thrown-when-moving-an-issue-to-another-type-in-jira-server/ . Meanwhile, convert it via Issue Navigator > Bulk Change > Move instead of the wizard — that path skips the broken validation.