JPD date field migration

[Barbora Vacková]

How can I migrate a date field from JPD to Jira? I created a JPD date field with the same name and type as the one we use in Jira, and I want to migrate this field into the original Jira Start date.

However, I’m getting this error:

The Jira Start date is also a Date field, so I’m not sure what is causing the issue.

The only thing that comes to mind is this: when I try to display the JPD “date field” in Structure, it doesn’t appear as a standard date field. Instead, it shows in this format:

{"start":"2026-01-01","end":"2026-01-01"}

Is it possible that this is the reason it cannot be mapped?

And if so, when will the JPD “date field” behave as a regular date field in Jira?

[Bill Sheboy · Accepted solution]

Hi @Barbora Vacková -- Welcome to the Atlassian Community!

You are correct that Jira Product Discovery (JPD) uses its own "date field" format, allowing it to store a single date, a date range, or a quarter.  It is a JSON expression, but represented as text.

There is no equivalent "date range" type for global fields, and so that is probably why the feature "Migrate field values to a global field" does not work:

https://support.atlassian.com/jira-product-discovery/docs/manage-space-and-global-fields-from-your-space/

Luckily, that migrate feature does not automagically delete the JPD field!  Instead, it performs the migrate of information and then lets you verify before you manually remove the JPD field later.  If we assume your JPD field only has a single date value (and not a range)...

A possible workaround would be using an automation rule with a scheduled trigger to perform the migration:

1. add your new global field, and either use or ignore the migrate feature
2. create the following automation rule below, and...
3. run it repeatedly until caught up (i.e., all the Ideas have the field filled)
4. now disable that rule as it is no longer needed
5. check some of the date fields to verify
6. add the new field to JPD views, and...
7. remove the old JPD field from any JPD views, perhaps keeping it for a while until ready to delete it from the space (i.e., project)

Here is the rule:

• trigger: scheduled, with JQL

project=yourJPDProject 
 AND yourNewGlobaField IS EMPTY
 AND yourOldJPDField IS NOT EMPTY
 ORDER BY Key ASC

• action: edit work item, to set yourNewGlobalField to this smart value expression

{{jsonStringToObject(issue.yourOldJPDField).start.toDate.jiraDate}}

That works by converting the old field's text with jsonStringToObject(), and then accessing the start attribute, converting it toDate type, and then using the jiraDate format to set the field.

In the expression, you may need to use the custom field ID rather than the name of yourOldJPDField.  To find that, please use this how-to article, or look for it with the smart value finder { } at the right-side of the field when editing it.

Kind regards,
Bill