Hi community,
Is there any way in cleaning up jira instance by removing unassociated field configurations.
I am trying to find a mechanism of deleting all field configurations that are not associated to project using groovy script and this needs to be scheduled as a job.
Thanking in advance.
Nope, the way you plan on doing this is pretty much what you need to do to clean things up.
So it just comes down to a lot of testing before you're sure it works exactly as it should, plus some maintenance over time in case Jira/API changes, but that's that - no built-in cleaners for this sort of thing.
A script for this would take quite a long time to write, and not necessarily be the best thing you can do for your admins.
It is far easier, quicker, and safer for your admins to simply remember to clean up as they go - every now and then, as they reconfigure Jira in a way that means schemes might become unused, nip into admin and tidy up the dead ones.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nic Brough -Adaptavist- @Radek Dostál ,
We do have cleanup scripts for other schemes like field config schemes, workflow schemes, screens, permission and notifications. Except for this cake of field config.
But if we get hold of some snippet for finding field configs which are unassociated to project is perfect right to make the environment cleaner from unwanted data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.