Recommended approach to replacing issue types

[shane-nz]

My business owner wants to globally replace an existing issuetype with another

The issuetype in question was a singular RAID item that captured all 4 risk objects (Risk, Assumption, Issue and Dependency) in conjunction with a custom field.
The request is to now have 4 independent issuetype mapping to each risk element.

One of the requirements is for staff to no longer be able to Create the old RAID issuetype.
Another requirement is to have old information still searchable/findable
 
I initially thought to migrate/move the existing issues to the new issuetypes then remove the old RAID issuetype

Have contemplated scripting this with Scriptrunner for Jira with removing RAID as an option from the create dialog, whilst keeping the old RAID issues for records keeping. I am not 100% confident this will disable create across all apps and features within Jira. 

Which of the two would be most recommended or is there any other way.

  

[Trudy Claspill]

Hello @shane-nz 

Have you considered starting a new project with the new issue types? Then change the permissions on the original project to remove allocation of the permissions that enable creating and updating issues, effectively making it read only. The historic data would be searchable. New issues of the old type would not be creatable if you don't include that issue type in the new project.