Cannot remove locked fields after disabling Jira Service management

[Jordan Accinelli]

I'm trying to clean up my Jira Custom fields, and there's a lot of stuff in there from a trail we ran with JSM. Even though JSM has been fully disabled, Jira is still considering the products to be fully locked.

Does anyone know how to properly clean up these fields after disabling JSM? Or is it just not possible?

Thanks!

[Nic Brough -Adaptavist-]

Welcome to the Community!

Removing an app shouldn't do this, but removing an application will.  They all stamp their stuff on your data (I don't think this is a bad thing - it means if you choose to go back to them, you get everything back, and if you don't, the data they leave behind isn't imposing any significant load)

But.

Disabling is a half-way house.  It stops things running, but does not stop it being loaded and it will continue to interfere with anything it thinks is JSM related.

If you decide you don't need it, you've done the right thing - disable it now, and see if your people tell you that they want it back.  If they do not, after a couple of weeks, then delete the application entirely.  After that, your people will not see the dead fields, and you'll be able to completely delete them without much fuss.

[Jordan Accinelli]

Hey, thank you so much get back to me!

I should clarify sorry, I meant I've removed the application altogether, not just disabled it - the team is set on not using it anymore, there was just a fundamental misunderstanding as to what JSM was for, and we're pivoting to use JWM for now.

I can't find any formal documentation around that offboarding process though, the only step I properly went through was removing it from the billing section under subscriptions, is there something else I need to do here?

Thanks!

[Deleted user]

Following for an answer as well. We removed JSM 3 years ago, but still have the locked fields and Opsgenie, neither of which we want to use.