AWS Thinkbox Discussion Forums

Request: Separate history of repo changes from job changes

We sometimes have issues where someone adjusts a repository-related setting (most frequently limit counts), and we want to know who it was and why. We have the upper limit on repository history entries set to 8192 right now, but that usually only gives us 1-2 days’ worth of history entries, which is almost never enough.

I think it might be helpful to separate the history of configuration changes to the repository (pools, groups, limits, repo settings, etc.) from the history of job-related operations (submissions, deletions, property changes, etc.)

+1 , we would find this really useful aswell.

Totally agree. Adding to the dev tasks, will come back with any flack. :smiley:

Privacy | Site terms | Cookie preferences