Import idea and issue with date format

[Michaël BELVAL]

Hi,

I try to import ideas on a project. All data are loaded except date. I tried everything with the wizard but impossible to load date. I try all possible format.

Is there any tips to help me for loading dates?

Thanks

[Nick Haller]

Hi @Michaël BELVAL ,

As @Tanguy Crusson , JPD date-fields use a custom format which is essentially a date range. So in order to import an idea (or ideas) into JPD, the dates will need to follow a similar formatting to work as expected.

For additional context - if you were to run a JQL within the Filters tab of your instance and check the JPD date-fields, you will see they do not follow a format such as yyyy-mm-dd, and instead a range:

✅ When exporting JPD ideas to a CSV from the Filters tab, the dates retain the range-formatting as shown above.

⚠️ When exporting JPD ideas from within the JPD project, the results differ and the dates export to a cleaner yyyy-mm-dd format. Having said that - if you were to import this back into JPD, there will most likely be problems mapping the dates fields as expected due to formatting...

I believe the date formatting you will need for this to work as expected is something like one of these depending on the date / range:

"{""start"":""yyyy-mm-dd"",""end"":""yyyy-mm-dd""}"

Day Example: "{""start"":""2024-02-21"",""end"":""2024-02-21""}"

Month Example: "{""start"":""2024-04-01"",""end"":""2024-04-30""}"

Quarter Example: "{""start"":""2024-07-01"",""end"":""2024-09-30""}"

For example:

We recommend following our documentation on how to correctly format a CSV during import, but again - I believe the date format needs to follow what's shared above in order for this to work as expected, and map the date fields normally.

Hope that helps. Let us know if you have any questions.

[Tanguy Crusson]

Hi Michael, I don't think you can import dates this way today unfortunately - because of the very custom format we use for dates in Jira Product Discovery. We'll consider this when we revisit the import feature

[Bill Sheboy]

Hi @Michaël BELVAL -- Welcome to the Atlassian Community!

Yes, and...to Tanguy's answer:

A possible work-around could be to import the field into a different custom field (e.g., Due Date), and then use an automation rule to set the JPD field (using their internal format) and then clear, or ignore, the value in the imported field.

FYI...I have not yet tried this.

Kind regards,
Bill