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

Automations for date fields

Neta Ilany

When using Automation rules on Ideas, I noticed that date fields on the Idea issue type are not available for automation rules.

The use case:

We have a custom field "Sprint start" (sprint number; select field), which we use to indicate in which sprint this Idea will start, as part of the HL planning.

I would like to "translate" these values into a specific date, by setting an automated rule (if Sprint Start = "1" then start date is 1/1/2024). This will enable Ideas to be visible on the timeline view, which uses DATES as input.

Currently, date fields are not supported in automation rules on Ideas.

Is this expected to change anytime soon?

@Tanguy Crusson

Thanks

Accepted answers

Rohan Swami

Hi @Neta Ilany it's not in our immediate plans to make improvements to Automation capabilities, though we have noted your issue for us to address when we work on this area in the future. I suspect the limitation here is that dates in Jira Product Discovery are actually a text field under the hood, we did this so we can support date ranges (eg. Delivery in Q1 instead of Jan 1 2023).

In case you haven't seen it already, here's a post with our supported Automations: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-demo-Automation-for-Delivery/ba-p/2057152

All comments

Rohan Swami

In case you haven't seen it already, here's a post with our supported Automations: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-demo-Automation-for-Delivery/ba-p/2057152

Christian Prats_sd1z4g

Hi @Rohan Swami
Any news on making dates in JPD actual dates so we can query them?

Thanks

Rohan Swami

@Christian Prats this isn't in our short term plans at the moment

František Soudek

@Neta Ilany @Rohan Swami @Christian Prats Figured out workaround:

First you want to find the name of your custom field you use in product discovery for date you want to set. You can follow this tutorial: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Once you have your custom field, you can set its value inside "More options" on create or edit issue action.

Snímek obrazovky 2024-02-26 v 18.07.26.png

The format is following:

If you want the date to be from 2024-02-04 to 2024-02-05:

{
"fields": {
"customfield_10185": "{\"start\":\"2024-02-04\",\"end\":\"2024-02-05\"}"
}
}
}

If you want the date to be set to 2024-02-04:

{
"fields": {
"customfield_10185": "{\"start\":\"2024-02-04\",\"end\":\"2024-02-04\"}"
}
}
}

If you want to use smart values (be sure to have it formatted right):

{
"fields": {
"customfield_10185": "{\"start\":\"{{triggerIssue.duedate}}\",\"end\":\"{{triggerIssue.duedate}}\"}"
}
}
}

Moran Bachar

@Rohan Swami

Hi,

Is there any update on this matter?

Welcome!

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