In most cases launcher legacy version was selected erroneously by user, so it should not be transferred to the duplicated report.
This was originally raised by @dericksonmark.
Approach
Support specifying a list of Jira version IDs for TransferVersionsModule which should not be transferred. The config.yml currently only contains the version ID of MCL version "1.6.93 (legacy)".
@dericksonmark proposed adding a ARISA_IGNORE_VERSION <version> tag which can be added to a report to prevent Arisa from transferring that version. However, that might be a bit cumbersome especially since a large amount (or nearly all) reports with "1.6.93 (legacy)" have selected it erroneously.
Purpose
In most cases launcher legacy version was selected erroneously by user, so it should not be transferred to the duplicated report. This was originally raised by @dericksonmark.
Approach
Support specifying a list of Jira version IDs for
TransferVersionsModulewhich should not be transferred. Theconfig.ymlcurrently only contains the version ID of MCL version "1.6.93 (legacy)".@dericksonmark proposed adding a
ARISA_IGNORE_VERSION <version>tag which can be added to a report to prevent Arisa from transferring that version. However, that might be a bit cumbersome especially since a large amount (or nearly all) reports with "1.6.93 (legacy)" have selected it erroneously.Checklist
docsfolder