Hi everyone,

As per my previous comment, I am closing this issue as fixed in JIRA 7.1.0.

With that said, after reviewing each comment and reviewing this issue with support engineers, I've concluded that there were multiple problems being reported against this issue. You may want to follow one of these other issues:

• Importing issues from Trello doesn't work properly, either because of...
  • An invalid issue type error – This problem is tracked in JRA-63625.
  • An error stating "data may be in an unstable state – This problem is tracked in JRA-63636.
  • An "IndexOutOfBoundsException" is raised – This is also tracked in JRA-63636.
  • A "Sub-task" issue type from Trello – This problem is tracked in JRA-59710.

For those concerned about the default issue type scheme: prior to JIRA 6.4, the default issue type scheme was automatically updated to contain every issue type. However, in JIRA 6.4+, a decision was made to change this behaviour – the reasoning can be noted in the discussion on JRA-59866. This has, understandably, caused some confusion; indeed, this issue was originally raised citing the default issue type scheme as the problem. However, the actual faulty behaviour was the move issue feature not working without all issues being present in the default issue type scheme; this has been fixed in JIRA 7.1.0.

If you have any questions or concerns, please don't hesitate to ask – I'm still listening

Cheers,
Chris.

Hi everybody,

I've spent some time understanding this issue. There appear to be two definitions for what this bug is:

1. People cannot move issues between projects, and
2. Issue types are not being added to the default issue type scheme.

Though I can see where (2) has the potential to cause problems, I've been focusing on and testing what versions of JIRA that (1) occurs in.

From my testing, moving issues between projects – where projects do not share issue type schemes, and the default issue type scheme does not include all issue types – works as of JIRA 7.1.0.

To echo a comment made by dmeyer on JRA-59866:

Hi everyone,

We do not plan to address this report. The behavior of the default issue type scheme in JIRA 7.0 and up is intentional and documented. As our documentation says "new issue type will be automatically added to the Default Issue Type Scheme". This does not mean that all issue types in JIRA, especially those defined in project blueprints from JIRA Software, JIRA Service Desk, and JIRA Core will automatically be added to the Default Issue Type Scheme.

Unfortunately, there are places in JIRA that make assumptions about the issue types present in the Default Issue Type Scheme. We will begin to address these on a case-by-case basis. For starters, we have reopened JRA-46227.

Regards,
Dave Meyer
Senior Product Manager, JIRA

Based on this context, and that moving issues between projects – the actual desired product behaviour – works in JIRA 7.1.0, I am planning to resolve this issue as fixed in 7.1.0.

To avoid conflating this issue further, if there are product behaviours other than moving issues that appear to be broken because of the default issue type scheme changes, we will raise separate issues for them. This will allow us to address restoring the desired behaviour rather than a special configuration.

Regards,
Chris.

JIRA (Dario Bonotto) please can you advise why this issue has been reduced to low priority (priority changed from low to medium, then medium to low)?  This defect is a significant barrier to using JIRA efficiently.

Even when I have two projects with a shared configuration (new feature of JIRA 7), moving an issue not contained in the default issue type scheme does fail due to the missing issue type. This is obviously nonsense, but I've lost 3 hours with this bug. And others will hit this trap also.

The suggested workaround with manipulating the JIRA configuration via SQL is not an acceptable way IMHO. Fortunately the "may help" workaround using "bulk move" did work for me. This should be the first option in KB [article|https://confluence.atlassian.com/jirakb/unable-to-move-issue-to-another-issue-type-due-to-the-issue-type-selected-is-invalid-error-227413483.html].

Moving existing issues to another project ist not unusual. And many customers may have own issue types not included in the default scheme. So the fix of the move functionality should be solved with a higher priority!

Reopened. See comment on JRA-59866.

Hi all,

We will be tracking this under JRA-59866

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

Yes, I am using JIRA Server.
I followed the instructions: Unable to move issue to another Issue Type due to 'The issue type selected is invalid' error
And because I am using H2 db (because we use it for training purposes), I found the doc Accessing JIRA's H2 embedded database very helpful. Doing the inserts fixed my problem.
But it seems to me that every new customer who downloads jira7 software would have this problem. Isn't that the case?

Hi, I'm able to easily replicate this problem in Cloud.

joanna.thurmann, I assumed you were using JIRA Server. This can only be fixed in the database, as described below:
https://confluence.atlassian.com/display/JIRAKB/Unable+to+move+issue+to+another+Issue+Type+due+to+%27The+issue+type+selected+is+invalid%27+error

I changed this bug to fit our template and to any more info, but I left your steps to reproduce there.

Saw that. Thanks. Your question there is the key... "what could cause a new issue type to not be in the Default Issue Type Scheme?"

Note the replication instructions above. The "Bug" issue type is NOT in my Default Issue Type scheme and I cannot add it now. So I am stuck. Perhaps because I installed JIRA Software but the first project I created was a Business type project. Not sure.... will create a support ticket.

Looks this is discussed in https://confluence.atlassian.com/display/CLOUDKB/JIRA+Cloud+%27The+issue+type+selected+is+invalid%27+during+Move+Issue+to+Another+Issue+Type
but is not yet fixed. I don't know if it is Cloud, Server or both