nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copy DateType Custom field from JDP to Jira

Sushil Ranjan_csk0y5

I am setting up an automation to sync or copy date fields between a Jira Discovery (JDP) project and JSM project.
So far, I am able to successfully sync the date from the JSM to JDP, but encountering issues when trying to sync from JDP to JSM

JSM FieldName : Deadline // customfield_11307
JDP FieldName : Deadline DP //customfield_11308

I understand that date field in JDP is 'actually an array of two text values representing dates (start & end)' therefore we cannot use JIRA date field on JDP, so I created JDP global field 'Deadline DP'. If there is a supported method to use a standard Jira date field directly within JDP, please do correct me.

Below is the automation for JDP -> JSM, I have separate working rule for JSM-> JDP.
trigger: Value changes
branch: for linked issues
Log action: Extracted start: {{triggerIssue.customfield_11308.substringBetween("start\":\"","\",\"end")}}
edit issue:
{
"fields": {
"customfield_11307": "{{triggerIssue.customfield_11308.substringBetween(\"start\":\"\",\"\",\"end\")}}"
}
}

Log action shows extracted date, but fails to update JIra field

I have tried other options like:
{
"fields": {
"customfield_11307": "{{triggerIssue.customfield_11308.match(\"\\\"start\\\":\\\"(.*?)\\\"\").get(0)}}"
}
}
Audit log:
Error editing issues
TP-218 (The Deadline must be of the format "yyyy-MM-dd" (customfield_11307))
Issues edited successfully
TP-218

Any help or clarification is appreciated.

Thanks,
Sushil

Accepted answers

Bill Sheboy

Hi @Sushil Ranjan

Your JSON expression likely has problems due to the nested, double-quotation marks.

The JPD date format is JSON stored as text, and with the recently added jsonStringToObject() function the values may be extracted:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#jsonStringToObject--

For example:

{{jsonStringToObject(issue.customfield_12345).start}}

That value will be text. When you need an actual date / time value, add toDate at the end of the expression.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Sushil Ranjan

Your JSON expression likely has problems due to the nested, double-quotation marks.

The JPD date format is JSON stored as text, and with the recently added jsonStringToObject() function the values may be extracted:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#jsonStringToObject--

For example:

{{jsonStringToObject(issue.customfield_12345).start}}

That value will be text. When you need an actual date / time value, add toDate at the end of the expression.

Kind regards,
Bill

Joel Tan_3ptl9a

is the JPD team planning to improve and introduce a way to have actual date format instead of string in the JQL export?

Sushil Ranjan_csk0y5

Thanks for the help Bill, it worked.
{
"fields": {
"customfield_xxxx": "{{jsonStringToObject(triggerIssue.customfield_yyyy).start.toDate}}"
}
}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-cloud

automation

jpd

jdp