Removing all JSM config from JIRA Server/ Data Center

[StephanieC]

We are planning to deprecate JSM by migrating the 5 JSM project over to "regular" JIRA Software projects. 

Once we migrate the projects - after creating ALL NEW projects, issue types, fields, screens, workflows, etc we will migrate all historic data/issues from the JSM projects to the JSR projects -  we plan to uninstall JSM. 

When we do this- will all of the projects, request types, JSM fields, JSM issue types, workflows, permission schemes, etc  disappear? Or will we have to delete them manually? 

Need to know for planning/ resourcing purposes. We are trying/hoping to "de-clutter" our admin panel. 

[Evgenii · Accepted solution]

Hi, @StephanieC 

If you want to remove JSM portal its' commonly enough to delete JSM projects. Of course, you can remove issue types schemes, workflow schemes and so on, but without JSM projects customer portal is useless.

[StephanieC]

We are deleting all of it of course. Our users dont like the portal - theyd rather create service desk tickets that way they do for all other (JSW) tickets. 

As noted, we are uninstalling JSM. My question is whether all of the stuff on the back end that is related to/created by JSM - such as issue types, permission schemes, JSM fields, etc disappears, or do we have to delete it manually?

[Evgenii]

@StephanieC can you please clarify, do you have 2 instances (one JSM, another one Jira), or you have one instance, for both products?

If it's 2 instances, then after removing JSM, everything will be deleted.

If it's one instance - then artifacts will remain, you'll have to delete them manually.

[StephanieC]

We have JSW and all of its plugins on a single server. Confluence is on a second server. So Im assuming now based on your reply that everything will need to be deleted manually.