Feature Request: Option to make the Change Log field required

Welcome to the community, Rob Yoder 🙂!

I like the idea of having the ability to choose your "Default Options" for the Desktop Image (or any of the other wizards) at the MSP-level but override it at the account level.

Playing devil's advocate for a minute, if we require "Change Log", will that just make it so techs are putting useless info in the Change Log field to satisfy the required field? Or, do you pair this with some kind of approval process where if they don't put in useful info in the Change Log, it request is rejected?

Our primary goal is to have a breadcrumb trail of changes made to the stock image in case it needs to be rebuilt at some point. We don't want to lose that history. The issue we face is that since the field isn't required, engineers set all the values and click save, forgetting to enter the notes. 

I could see the usefulness of an approval process for some environments. It may already be possible to accomplish that by using the existing approval process, although I'm not certain what the person getting the approval request sees—whether the request includes the change log field values.

We would handle engineers not entering valid data as an employee management issue, the same as if they don't provide proper documentation for the work they're doing in our ticketing system.

Even better!
Have the system support your process, but don't expect the system to enforce your process. Love it!

I would also like to have this feature, any update on adding it?