TBH there's not much I can say on this as its not my particular area of focus (I'm the "bring CD to everyone" kinda guy) but I and other community members do recognise it is a problem that we want to solve. With Pipeline there is a trend to moving job configuration to source control and I think that direction will make things more Ops friendly as time goes by.
I wouldn't call it just a trend, it's part and parcel with the DevOps philosophy. Infrastructure as code, in source control. It's more of a conclusion, the trend is adoption.
Not only job configuration. But the entire configuration of your jenkins setup.
For example this issue was a blocking factor for automatically provisioning a new jenkins.
https://issues.jenkins-ci.org/browse/JENKINS-34035