Our SQL DB for Jira has huge hourly transaction logs for some specific tables used by 'Automation Lite for Jira' (mentioned below). Is there a way to limit the amount of detail in the auditing going on. We don't want to eliminate the auditing, but the large hourly transaction logs are getting crazy.
We have written up an article on how to expire items from these tables - https://codebarrel.atlassian.net/wiki/spaces/AUTO4J/pages/55665606/How+to+expire+items+from+the+audit+log
We do have plans to add this functionality into the product but I can't give a date for this yet.
Co-Founder @ Code Barrel
Hi @Nick Menere,
i saw things have changed in the meantime:
"If you are running Automation for Jira 3.12+ then audit log expiry can now be configured by global administrators!"
But what is a global administrator?
I have Automation 3.12 plus Jira Admin and Sysadmin global privileges, but i dont have that setting.
A Global administrator is just a normal Jira administrator. We use Global Admin to distinguish from Project Admins.
Go to the Global Admin page for Automation and use the drop down in the top right and click on Global configuration:
We blogged the details about this at: https://blog.codebarrel.io/time-to-expire-those-audit-log-entries-f7dddec3a655
Hope that is what you are after.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs