Issue Types on Create dropdown do not match Issue Type Schema definition

[Shannon Davis]

I am on JIRA 6.3.x

I have set up a project with its own Issue Type schema.  After a month or so, they came to me and told me that many of their issue types had gone missing. I checked their project and its associated issue type schema - and it was still OK. However, I was able to replicate their problem - when i went to "Create" an issue in their project, the Issue Types list was quite small (and included one that doesn't exist on our server!)

I can't fathom why this is happening.  Any ideas?

(These folks do have project admin, but I am not sure what they could have done to cause this).

[Shannon Davis · Accepted solution]

Solution: Change to a different workflow scheme. Reassociate to the original workflow scheme. Reindex.

[Nic Brough -Adaptavist-]

Check Joe's answer first, but the second thing is to look at the two types of type you can define (that's a horrid sentence, but bear with me).  An issue type can be either an issue type or a sub-task issue type.

Only issue types appear on "create" because sub-tasks can only be created from their parent issue. 

But, I suspect Joe is right.

[Joe Pitt]

If you've check the schema and the project to make sure they are using the schema I'd open an issue with Atlassian support.