Issue type not shown in create menu even if it is in schemes

[Lubos Valco]

I have 2 projects with the same issue type scheme, workflow scheme, screen scheme, permission scheme, notification scheme. Field schemes are not much different.

When clicking native create on the project even as admin I can not see the same dropdown for issue types - 1 issue type is missing in one project but I can see it in other project.

There are no restrictions in workflows, no behaviours attached to these projects, the whole instance was reindexed, jira version is 8.x

I am not sure why this is happening and how to check if plugins are interfering. I'm afraid that this is a database issue but I don't know how to check that as well, what could I do? we need that issue type there.

[Jack Nolddor _Sweet Bananas_ · Accepted solution]

Hi Lubos,

Note that only standard issue types can be created with no parent using the top Create Button.

Others need to be created within a parent issue (that is on the issue view screen using Creating Subtask menu)

What kind of issue type is the missed one? Standard or Subtask?

See Administration >> Issue Types:

Regards

[Lubos Valco]

Hi Jack,

It is a Standard issue type. I can create this issue type on second project with the same issue type scheme but in this one I can not see it in the dropdown

[Jack Nolddor _Sweet Bananas_]

Have you any third-party app that can hide this kind of field?

See Behaviours included within Script Runner for Jira, Issue Type Filters (and Security) application or any of this kind.

Regards

[Lubos Valco]

Yes as I mentioned I tried checking ScriptRunner's behaviours but for other plugins I am not sure. I came to this messy JIRA instance without a handover but this problem just appeared. It wasn't present before and I didn't do anything with this project or issue type. It just happened one day without a reason.

We do have many plugins - is it possible to track their impact somehow instead of disabling one by one?

[Jack Nolddor _Sweet Bananas_]

Sadly, not.
You may find useful to run the Safe Mode for a while to see if the problem persist.

Regards

[Lubos Valco]

Hey Jack, thanks for help. It was indeed one of the plugins. I had to deactivate and activate plugins one by one because pressing safe mode was timed out from the server (there are too many plugins installed...). But in the end I was able to find the rootcause.

[Brian Mertens]

@Lubos Valco Which plugin was the problem?

[Lubos Valco]

@Brian Mertens Back in the days I was new to the instance and wasn't aware that also PowerScripts were used by some admins... disabling plugins one by one outside of office hours or on staging environment should help you identify such bugs