-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
4
-
Title :
Disable populating the database table AO_733371_EVENT_PARAMETER table when Batching feature is disabled
Summary :
Currently, even if the Batching notifications is disabled in Jira, the application still writes to the table AO_733371_EVENT_PARAMETER in the database.
Steps to replicate
- Disable batched notificaitons
- Make any random update to any Jira ticket
In this case, this table keeps recording rows related to these actions.
Expected results
This table should not record new rows related to these actions, since they are not used because the batched notifications are disabled.
Actual results
This table keeps recording new rows related to these actions.
Workaround
The only way to disable the writing into this table is by disabling the below system plugins.
Not suggested to for prod environments as it may cause multiple other issues
The below plugins have to disabled in the same order as below and should be enabled back in the reverse order* -
- Jira inform - batchers
- Jira inform - batching plugin
- Jira inform - event plugin
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
[JRASERVER-73249] Disable populating the database table AO_733371_EVENT_PARAMETER table when Batching feature is disabled
+1 Agree, how about retention policy?
at the moment, 4mln records in that table 
This table is getting bigger and bigger, even if you are not using it.
It would be also neccesary to have a way to purge this data periodically.
We have email digest and we dont need this type of data at all.
The table is not 12g of data with 37733699 rows. Do disabling batchers really has a impact or other issues ?
On our side it was found if its disabled, the health check plugin does not work, then also roadmap in jira 9