problem with field configuration schemes

[marçal martorell]

The field configuration scheme was never set by default  which means that there is no scheme at all.(something called: "System Default Field Configuration"(not scheme))

the problem comes now, that i need to change the scheme of field configuration depending on the issue type.

"System Default Field Configuration" is not an scheme and doesnt allow me to configure it like a field configuration scheme.

the solution is to change the default field configuration for a new scheme.

the thing is that i have like 600+ project/containers with the default setup and I dont have time to change them manually one by one, is there a way to change them all at once?

thanks,

[Nic Brough -Adaptavist- · Accepted solution]

I'm afraid you need to change all of them manually.

Unless you have something like ScriptRunner which can run a script to go over all the projects and change schemes.

[marçal martorell]

damn.... 

good thing, I actually have the ScriptRunner extension,

but i dont know how it wokrs... I will work on it

thank you

[WW]

So, when you normally change a field configuration scheme through ScriptRunner using the Jira API, you have to remove the old scheme, then add the new scheme, otherwise, you'll seriously break Jira.

When you try to remove the scheme, System Default Field Configuration, it gives a null pointer exception.  So, the scheme really does not exist!

2021-07-26 10:59:31,735 ERROR [common.UserScriptEndpoint]: Script console script failed: 
java.lang.NullPointerException: Cannot invoke method getId() on null object

If you catch the exception, or if that's the only scheme you're changing, then you can still add the replacement scheme.