Automation to Track Start and End Dates in Jira Product Discovery

[elyn]

I’m trying to set up an automation rule in my Product Discovery board to automatically track when a ticket moves through specific statuses, but I keep running into errors.

Goal:
I want to automatically record two custom date fields — Start Date and End Date — based on ticket status changes:

• Start Date: when the issue status changes from “Design To Do” to “Design In Progress”

• End Date: when the issue status changes to “Done”

What I’ve tried:

• I created two custom date fields: Start Date and End Date

• I attempted to create automation rules that use the “Edit issue fields” action to set the current date (using the “{{now}}” smart value) when the status changes as described above.

• However, the automation keeps failing with error messages such as:

  • “Field does not exist”

  • “Unable to log the date value”

[Christos Markoulatos]

Hey @elyn 

The errors happen because Jira Product Discovery date fields aren’t standard date pickers—they store ranges in JSON. Automation fails if you try to set them with {{now}} directly.

Here’s the quick fix:

• Use Advanced JSON in the “Edit issue” action instead of the dropdown:
  {

    "fields": {

      "customfield_12345": "{\"start\":\"{{now.jiraDate}}\"}"

    }

  }
  For End Date, set "end" instead of "start".
• Find the correct customfield_xxxxx ID via the REST API or smart value finder.
• Make sure the rule actor has edit permissions in JPD.

Links that help:

• Advanced field editing with JSON
• Smart values for dates

Hope this helps!

[Bill Sheboy]

Hi @elyn -- Welcome to the Atlassian Community!

First thing: Jira has a built-in field named "Start Date" so using the same name could lead to confusion / errors.  From what you describe, I recommend renaming your fields to "Design Start Date" and "Design End Date".

Next, Jira Product Discovery (JPD) has its own date format, using a JSON expression represented as text to hold a single date, a date range, or a quarter.  It looks like this:

"customfield_12345": "{\"start\":\"2025-10-15\",\"end\":\"2025-10-15\"}"

Please note both parts (start and end) are required even when only specifying a single date value.  For your case, you likely want to set them to the same value: {{now.jiraDate}}

"customfield_12345": "{\"start\":\"{{now.jiraDate}}\",\"end\":\{{now.jiraDate}}"}"

Using that information, you may set the field value using a JSON expression as Christos described, however...

Think about how your team works: do designs every move backwards in the workflow?  If so, consider what you want to happen to those date fields.  For example:

• When a design moves backwards from Done to In Progress, should the "Design End Date" field be cleared?
• When a design moves backwards from Done to In Progress, should the "Design Start Date" field reset to the current date or should it remain unchanged to show the complete duration of in-progress time?  If it should remain unchanged, your rule would need an additional condition check to only set "Design Start Date" when it is already empty.
• What should happen if someone manually changes one of the date fields?
• etc.

Finally, if you need to access the values in those date fields in other rules, they may be accessed using the jsonStringToObject() function:

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

Kind regards,
Bill