-
Suggestion
-
Resolution: Unresolved
-
None
-
86
-
20
-
Problem Definition
Insight currently keeps a history whenever there is an update to any of the objects' Attributes (with a NEW Value), a new row will be added to AO_8542F1_IFJ_OBJ_HIST table.
This table can increase dramatically in size.
Suggested Solution
Possibles solutions:
- May be a service retention period or cleanup mechanism in Insight to allow users to specify the criteria for deletion.
- May be a feature to exclude an attribute or object type from recording history. This would be very useful on objects or attributes that are updated automatically by automated imports with very large data.
- May be a feature to allow admins to limit the number of characters or size within a TextArea attribute in Insight, it might help to reduce Object's History table size
Workaround
Currently, to remove/reduce Object's History table size, a Database query to delete rows from the AO_8542F1_IFJ_OBJ_HIST table needs to be run.
Detailed workaround is published in this KB: Insight - How to delete Object History logs
[JSDSERVER-8706] Create a cleanup mechanism to Assets Object History
This is a vital feature that needs to be added ASAP. We're heavy Assets/Insight users, and have a number of objects with very long histories and long lists of comments. When we go to one of these objects, it often locks up the browser trying to load them all.
At least an interim measure of making the comments and history section paged, so it only loads the 10 most recent would help.
That "deleteObjectBean()" method is to delete the object altogether. I haven't found a method to delete just history items. Either selectively or even completely (the Jira ChangeHistoryManager API has a removeAllChangeItems method but no methods to delete certain change items).
Anyone tried using scriptrunner to delete history items? The javadoc has a findObjectHistoryBean() method, and a deleteObjectBean() method.
After some analysis, we've spotted that on object view history is being displayed using endpoint which limits records to 10 per page. Having that on schema view would also be handy.
A feature to define number of records visible in object history could also do the trick. For instance display last 10 records, if required history section could be expandable to present remaining records.
Dear Atlassian, it really is 'less than stellar' that you explain how to clean up your own construction, but at the same time states that it's none of your problem if we try to follow your suggestions and run in to problems,
Explanation: https://confluence.atlassian.com/jirakb/insight-how-to-delete-object-history-logs-1076827402.html
And then the thick disclaimer from the same page:
"Atlassian Support Offerings
The following approaches that involves SQL queries are beyond Atlassian Support Offerings. Please note that Atlassian does not support direct database INSERT, UPDATE or DELETE queries, as they can easily lead to data integrity problems. Atlassian will not be held liable for any errors or other unexpected events resulting from the use of the following SQL queries."
I'm eager to see if my current Jira issues ends up on this specific 2,5yrs old ticket page due to object history...