JPD: Automation to Update Custom Date Field Upon Action

[Andy Fieweger]

(Still looking for help on this issue I'm having)

Struggling with what I think should be a straightforward Jira automation.

Because Jira doesn't support using the Target date field for group by period (Year, Quarter etc), I've created a custom date field "Computed Target" and created a flow that evaluates the Roadmap field value such that when equals "Completed", then the custom field will get updated with the current date (date the user has updated the roadmap field.  Its not a perfect solution but its not terrible.

Here are the screenshots of the configuration.

[Gor Greyan]

Hi @Andy Fieweger

Happy that you could find the Field ID.

Adding what @Gabriela mentioned, another way to troubleshoot this is to add a temporary Log action before the Edit work item action.
For example, log the value you are trying to set into the date field, such as:

Roadmap value: {{issue.Roadmap}}
Target date value: {{now.jiraDate}}

This will confirm whether the rule is receiving the expected value before it tries to update the custom date field.

I would also temporarily hardcode the date value in the Edit work item action, for example:

{
"fields": {
      "customfield_XXXXX": "2026-07-07"
   }
}

If the hardcoded value works, then the field ID and field format are correct, and the issue is likely with the smart value.

If you can provide a screenshot from the audit log showing what it returned, we can help you further.

Thanks.

[Gabriela]

Hi @Andy Fieweger — Gor's route works, but the cleanest way to verify the exact ID Rovo handed you is to open https://your-site.atlassian.net/rest/api/3/field in a browser while logged in, then Ctrl+F for your field name. The value beside it, customfield_XXXXX, is what your automation should reference. That endpoint lists every field including JPD ones, so it sidesteps the fact that JPD project fields don't always expose the Contexts screen the way regular custom fields do. If you'd rather stay in the UI, Settings → Issues → Custom fields now lets you switch on a Field ID column showing the same value.

[Andy Fieweger]

Thanks @Gabriela  and @Gor Greyan as I now know how to find the UNID!  However, I've confirmed that I do have it correctly.  I'm wondering if either of you can move on to the next diagnostic of my challenge - which is getting the flow to work correctly.  thank you!

[Gabriela]

Hi @Andy Fieweger, glad the field ID checks out, so it's the write that's failing rather than the trigger. Setting a JPD date field from automation with a JSON / {{now}} value is a known one that errors, and Atlassian has a KB with the exact value format to put in the Edit issue action: https://support.atlassian.com/jira/kb/to-set-date-type-custom-field-via-automation-rule-when-using-json-value-now-throws-an-error-in-jira-product-discovery-project/. Also worth confirming the rule's actor has permission to edit the idea, or the write silently won't save. If it still errors after matching that format, paste the exact message from the rule's audit log and I'll take another look. Best, Gabriela

[Gor Greyan]

Hi @Andy Fieweger

Welcome to the Atlassian Community!

If you're just looking to verify the custom field ID, you can do in this way:

Go to Jira settings ->Work Items -> Custom fields, locate the field, click on Contexts and Default Values, and check the URL. You'll typically see something like customFieldId=12345..

That is your customfield ID.

[Henry Collins]

Bro, I'm trying to comment but this community is not letting me do this. They are saying your comment has formatting error. blah blah blah....