I would like to build some kind "pipeline" for configuring my plans:

plans > configure names > configure descriptions > configure notifications > configure permissions...

Example: All my plans should have the repository url/name in the description (as per your best practices). Currently I have these options to do that:

• Set it manually on each plan
• Set it manually on each plan by using some "description factory" method so that at least the url is only in one place
• Track all required properties in my own class and only create the Bamboo Plan instances after my "pipeline"
• Use reflection to access the "description" field so that I can loop through the plans and append the url to each one of them

The last option is close to what I want to do, but accessing a private field through reflection is obviously not really the best idea.

I think it would be very simple to just expose most fields through getter methods. There may be fields which should not be directly exposed, but in most cases this should not be a problem at all.

Another example would be that I want to add some default permissions, notifications depending on some rules that can be centrally defined. This would be in particular useful for temporary settings that could be easily applied to certain plans.