How can I delete issue with issue type empty in Jira?

[Sema YILDIRIM]

How can I delete issue with issue type empty in Jira?What can I do?

[Iván ISS]

Hello,

I know this is an old question that still remains unanswered, and it seems that there is no documentation available regarding this bug.

We have managed to add the 'Issue Type' field to existing issues using the 'External System Import' feature. To do that, follow these steps:

• Create a .CSV file that contains at least the columns for the 3 mandatory fields: 'Summary', 'Issue Key', and 'Issue Type'. Fill the columns with the data from your problematic issues.
• Go to 'Jira Import Wizard' or 'Import External Issues' (https://your_jira_instance/jira/secure/admin/ExternalImport1.jspa ) and select 'CSV'.
• Choose the .CSV file you just created and select the appropriate file encoding.
  Select a project to import the data into.
• Map all 3 fields (or any other fields you need to fill in those issues). Check the "Map Field Value" checkboxes.
• Click 'Next' to begin the import process. Once finished, your issues will have the 'Issue Type' field, and you will be able to open, work with, edit, or delete them.

I hope this information is helpful for other users.

[Luis Gómez martinho]

This solution fixed the problem

[Jack Brickey]

I have no idea how you can have an issue w/o a type. however, to delete an issue (generally a bad idea) you can do that by going to the issue and selecting delete from the ellipses drop down in upper right. As long as you have delete permissions.

[Nic Brough -Adaptavist-]

I've been able to get to a broken issue type like this in a few different ways.  But only on Server.

You've partially deleted the issue type, without going through the integrity checks.  This is not possible on Cloud, so I'm questioning that label!

Anyway:

• You can break anything with Scriptrunner if you try hard enough (but when I did something like this with SR, I didn't do as much damage - everything still worked fine with an issue type with a blank name, you just couldn't search properly). 
• This probably applies for bugs in plugins, they may have code able to do similar damage
• You might get to a broken state by starting to delete an issue type and having the server crash/get-killed while it was trying to do the migration checks
• Finally, it's an absolute doddle to wreck your Jira by using SQL on the database, and that is what I'd be looking at first

How you got there might not be too important directly, but it keeps my potential fix route list shorter:

• Run the integrity checker, working through every issue and workflow related check (for larger Jira installs, only run one check at a time, otherwise it may time out without offering you the chance to fix stuff)
• After the integrity check, re-index what you can (the project index will do, you don't need the full locking or full but non-locking ones)
• If you did manage to do this via SQL, and the two above don't at least put you back in a place where you can at least migrate to another type, then we can talk about fixing it with SQL itself, and then how to stop people ever using SQL again.

[Sema YILDIRIM]

Thank you for the answer. I'm Jira admin. Not related to permission :(. The issue type information of these issues is deleted. It does not perform any operation on these issues. I get an error when I want to change the sample workflow scheme.