We're currently blacklisting the properties step from usage within the model, and we're going to stay that way - it can cause waaaaay too much confusion when executed outside of a central control. But that means we need to provide configuration sections for job properties. I'd like to do that as three separate sections - one for each of build parameters, triggers and other job properties.

My reasoning is that the catch-allness of properties is part of its confusion - you can only call it once per Jenkinsfile and you have to have every JobProperty you care about defined in it. I want to add a layer of abstraction over that - the three groupings (parameters, triggers, misc) make sense as three separate sections with different syntax.