Problem Definition

As part of the fix in JSWSERVER-15748 DVCS data is move to the different table AO_E8B6CC_CHANGESET_MAPPING.
For the busy and large instances, this table can grow quite significantly (4GB+), that will eventually slow down the CRUD operations and make it harder to main the Jira instance, due to large size (disk space, backup space).

Suggested Solution

Add options to have clean-up of old DVCS data, possible ideas:

• periodic clean-up job
• consistency check for existing issues
• deletion of the data as part of project deletion
• deletion of the data as part of issue archiving (partial data loss)

Workaround

None