I've noticed that my job configuration history is "spammed" with changes that the system, not a user, makes.
The changes in mind concern "changelogFilename" (if I remember correctly) and seems like it should be a property of a build, not a job, and thus not appear in the job configuration history.

The job configuration history pages take a very long time to load because of all these changes, and it's difficult to spot the real changes, where a user has changed something in the configuration.
Is this an issue with the plugin (for reporting it as a change) or in core (for having this info on the job)?