I would like to be able to log a field that records WHY a maintenance job was run. This should be filled in every time a maintenance job is triggered and it would be stored next to the other details. This would make it easy to see retrospectively for example WHY Fatal events were changed back into Regular ones.
It might also be an easy way of enriching reports with this information. You might want to consider a separate improvement to log a notice through maintenance that does not change any records but which does add this 'audit' level of detail i.e 'we did a release here' etc.
If you provide an API for this, then you could even hook in CD tools like Octopus onto this flow.
We are releasing a journaling feature for updates made to checks in the upcoming release. This particular idea is however not covered by that but the journal could be updated to accomadate this. We will keep it as Future consideration until we have a more detailed plan for this.