Hi Community, I'm trying to sync a "Planned Delivery Date" from a JPD field to a linked Jira Epic. My Setup: * Automation Rule triggers when a JPD Idea is linked to an Epic. * The rule is configured to edit the linkedIssue (the Epic). * I'm pulling the value from a JPD field (customfield_XXXXX) whose value, according to the API, is a JSON string (e.g., "{\\"start\\":\\"...",\\"end\\":\\"..."}"). * My Smart Value for the date is: {{triggerIssue.customfield_XXXXX.jsonParse.end.jqlDate}} (intended to parse the JSON string and extract the date). * I'm writing the value into a Debug Text field on the Epic. The Problem: The Automation Rule shows SUCCESS in the Audit log, but the Debug Text field on the Epic remains empty. The JPD field is populated, IDs are confirmed, and the rule structure is set to linkedIssue. Question: Why isn't the Smart Value (with jsonParse) resolving to a value, or why isn't it being written to the field? Any debugging ideas would be greatly appreciated!

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; } } }

Roadmap Derivation - Automation (HELP NEEDED)

Sebastian Pechhold

Hi Community,

I'm trying to sync a "Planned Delivery Date" from a JPD field to a linked Jira Epic.

My Setup:

Automation Rule triggers when a JPD Idea is linked to an Epic.
The rule is configured to edit the linkedIssue (the Epic).
I'm pulling the value from a JPD field (customfield_XXXXX) whose value, according to the API, is a JSON string (e.g., "{\\"start\\":\\"...",\\"end\\":\\"..."}").
My Smart Value for the date is: {{triggerIssue.customfield_XXXXX.jsonParse.end.jqlDate}} (intended to parse the JSON string and extract the date).
I'm writing the value into a Debug Text field on the Epic.

The Problem: The Automation Rule shows SUCCESS in the Audit log, but the Debug Text field on the Epic remains empty. The JPD field is populated, IDs are confirmed, and the rule structure is set to linkedIssue.

Question: Why isn't the Smart Value (with jsonParse) resolving to a value, or why isn't it being written to the field? Any debugging ideas would be greatly appreciated!

Screenshot 2025-05-22 at 12.41.01.png

Accepted answers

Bill Sheboy

Hi @Sebastian Pechhold

First, there is no "jsonParse" function in automation rules. What is the source where you learned that function as it is incorrect? Some chat / bot perhaps?

There is a jsonStringToObject() function that will help parsing the JPD date format: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#jsonStringToObject--

For example, to get the end date please try this:

{{jsonStringToObject(triggerIssue.customfield_12345).end}}

That value will be text. When you need it as a Jira date format, add the toDate function:

{{jsonStringToObject(triggerIssue.customfield_12345).end.toDate}}

Next, what is your rule scope: single-project, multiple-project, or global? The default is single-project scope rules, and they cannot modify work items in other projects.

Finally, your rule shows no branching. How will it access the JPD date field in the Idea to update the Epic's field?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Sebastian Pechhold

First, there is no "jsonParse" function in automation rules. What is the source where you learned that function as it is incorrect? Some chat / bot perhaps?

There is a jsonStringToObject() function that will help parsing the JPD date format: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#jsonStringToObject--

For example, to get the end date please try this:

{{jsonStringToObject(triggerIssue.customfield_12345).end}}

That value will be text. When you need it as a Jira date format, add the toDate function:

{{jsonStringToObject(triggerIssue.customfield_12345).end.toDate}}

Next, what is your rule scope: single-project, multiple-project, or global? The default is single-project scope rules, and they cannot modify work items in other projects.

Finally, your rule shows no branching. How will it access the JPD date field in the Idea to update the Epic's field?

Kind regards,
Bill

Sebastian Pechhold

Hey @Bill Sheboy ,

thank you. I changed the setup:

Screenshot 2025-05-23 at 08.53.09.png

To answer your previous question. Yes, i used Gemini before i got here

Project Target field (JPD) is not empty. It has a single date or a date from/to (mostly quartery)

Date format month June:

{\"start\":\"2025-06-01\",\"end\":\"2025-06-30\"}

Time frame format Q2 April-June:

{\"start\":\"2025-04-01\",\"end\":\"2025-06-30\"}

it is always the same "string" in postman.

Goal:

Transfer/sync this date to the linked epics/initiatives.

With my current setup, no actions were performed.

Bill Sheboy

Please post an image of the audit log details for the rule execution, expanding all the areas at the right side. That may show why the rule did not update as expected.

Also, did you confirm the rule scope is multiple-project or global? Otherwise that branch will not "see" the linked issues.

Sebastian Pechhold

Thanks for your patience. I just linked an Epic to the idea. Nothings happens.

Screenshot 2025-06-04 at 11.29.43.png Screenshot 2025-06-04 at 11.30.00.png

Welcome!

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

Quick Links

Find more posts tagged with

jpd