Issue importing CSV with Baseline Date field

Question

Hello everyone,

I'm facing an issue when importing a CSV file into Jira.

My CSV contains a Baseline Date field (date type), but during the import process Jira does not seem to recognize or properly map this field. The values are present in the CSV and use a valid date format, but after the import the Baseline Date field is not populated.

Has anyone experienced a similar issue with date fields during CSV import?

* Which date formats are supported for custom date fields during CSV import?
* Are there any specific requirements for mapping a custom field such as "Baseline Date"?
* Is there any additional configuration that needs to be checked before importing?

Any guidance would be appreciated.

Thanks!

Matthew Sinclair · Answer

Maybe its possible to have the sitting somewhere as an attachment or maybe in Confluence - let rovo tear into it and adjust it?

Something to experiment on in my future I suppose.

Tomislav Tobijas · Answer

aitbenhidafatimaezzahra24  I've been struggling with this too 🫠

It depends partly on what formatting your device uses and what Jira accepts. Once, I spent half of the day debugging it 😅

Apart from what guys have said above, I've found out that an easier solution could be, once you do the import, to ask Rovo to update those values based on the CSV file you provide to it in the chat 😄
*although, if you do importing occasionally, it would make sense to find a robust solution and format that actually works

Cheers,

Tobi

Josh · Answer

CSV import is picky about both format and field mapping for date fields.

* Use a single format for the whole column, typically dd/MMM/yy (e.g. 01/Oct/26) or ISO yyyy-MM-dd. Mixed formats in one column often map but leave cells blank.
* On the mapping screen, explicitly map your CSV column to the Baseline Date custom field (do not leave it as “Don’t map”). If Baseline Date does not appear in the destination list, the field is not on the target project’s screens / create context, or it is provided by an app and is not importable as a plain date field.
* After import, open one issue → check History. If the field never changed, the mapper skipped it.

Also confirm “Baseline Date” is a Jira date picker field you created (or from a specific Marketplace app). App-owned fields sometimes need the app’s own import or a REST update after issues exist. If you share whether this is a native custom field vs an app field (and one sample CSV row), we can narrow it further.