Allow 'Import Issues from CSV' function to populate ARJ Target Start and End date custom fields

At present, it is possible to use Jira 'External System Import' function to import a .csv with Jira Issues and map fields to Advanced Roadmaps fields of 'Target start' and 'Target end' custom fields. This is inclusive of choosing a custom date format during import to match the format of field dates in the .csv file. Jira Admin is required for this approach.

Attempting to import the same .csv via Jira 'Import Issues from CSV' function (non-Jira admin users can access this function) does not allow facilitate successful import when attempting to map to 'Target start' and 'Target end' custom fields and specifying a custom date format.

An example error during import is:

Ideally import would be successful via both .csv import tools.

Workaround

Using the External System Import, It is possible to import the fields “Target start” and “Target end” fields only if in the CSV file we make sure that these dates are in the format “dd/MMM/yyyy” (i.e.: 16/Aug/2023) - independently from the date format which is configured in the import config file for other date fields.

When importing, the date format mapping can even be other, but in the file the format of these specific fields needs to be the above.