Issue Summary

Introduce a new control column (e.g. ACTION) in the JCMA remediable CSV export that allows admins to explicitly mark certain entities to be skipped (e.g. with a SKIP keyword) during remediation and migration. This would enable more efficient handling of legacy or unwanted data such as old filters, boards, and other entities.

The current remediation feature in JCMA has been very helpful and has recently allowed us to fix a large number of errors automatically. However, in many real-world migration scenarios, customers do not want to migrate all of their historical configuration and data.

Common examples include:

• Old or unused filters

• Legacy or abandoned boards

• Other entities that are no longer relevant in the target cloud instance

Right now, we need to:

1. Identify these entities in the JCMA remediable CSV.

1. Manually clean them up or delete them either on Server/DC or after migration in Cloud.

1. Re-run or adjust remediation accordingly.

This is time‑consuming and error‑prone, especially on large instances with many projects and configuration objects.

Steps to Reproduce

1. Run JCMA remediation and download the remediable CSV file.
2. Review the CSV to identify entities (filters, boards, etc.) that the customer does not want to migrate.
3. Manually delete or clean up these entities on the source (Server/DC) or in the target (Cloud) after migration.
4. Re-run remediation and/or adjust the migration plan to reflect the manual cleanup.

Expected Results

Admins should be able to use the JCMA remediable CSV to:

• Flag specific entities that should not be remediated or migrated (for example, legacy filters/boards).

• Avoid having to manually delete or clean up these entities outside of the remediation flow.

• Run remediation and migration once, with JCMA honoring the skip instructions from the CSV.

Actual Results

• The remediable CSV does not provide a way to mark entities as “do not migrate”.

• All entities listed are treated as candidates for remediation and migration.

• Admins must perform manual cleanup and rerun parts of the migration flow, which adds overhead and risk of human error.

Proposed Solution:

Add an explicit “skip” mechanism to the JCMA remediable CSV, for example:

• Introduce a new column, such as ACTION (or MIGRATION_ACTION).

• Allow supported values like:

• • REMEDIATE (default / current behavior)

• • SKIP (do not remediate or migrate this entity)

• During remediation/migration, JCMA would:

• • Process rows marked as REMEDIATE as it does today.

• • Ignore or exclude rows/objects marked as SKIP from remediation and migration.

Alternatively, if introducing a dedicated column is not preferred, the feature could be:

• A dedicated “Skip” column with a simple keyword like SKIP or TRUE.

• Or a filtering UI option in JCMA that reads the CSV and lets admins exclude selected rows/entities before running remediation.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available