Does this setting change need to have an audit log?
Technical Implementation Proposal
Copy the exact implementation that we already use in the ProjectCiCdSettingChangeAuditor. This new setting lives right next to those two, so tracking should live in the same place for settings that live in the same place.
0 of 1 checklist item completed
· Edited by
drew stachon
Jackie Porterchanged title from Consider adding an audit even for changing skip_train_allowed setting to Consider adding an audit event for changing skip_train_allowed setting
changed title from Consider adding an audit even for changing skip_train_allowed setting to Consider adding an audit event for changing skip_train_allowed setting
@carolinesimpson I think this goes nicely with our feature set that drew has been working on and I do think we should add tracking for it in order to adequately ensure commit history accuracy. Can we get a weight prior to the 1st of Nov?
The analytics instrumentation label is automatically applied when featureaddition and workflowready for development labels are applied. We encourage teams to plan for instrumentation at the time of feature development for new features. This label helps ~group::analytics instrumentation to proactively reach out to teams that require instrumentation support. In case instrumentation does not apply to this feature, please feel free to remove the label.