Feature Request: JPD date as well as date range custom field

[Stas Hagemans]

Hi All,

This is a followup to the question which you were involved with last month. I did not want to muddy the waters with a slightly different question in the comments. 

Like Jerry, we are working on automations that are linked to a custom date field. As you stated that field holds a range, and should accept a single date. Storing a single date gets this error. (either hardcoding a date, using now/today etc etc)

Error editing issues
ROAD-5 (We couldn't save your changes. Copy your content, then try reloading the page.)

As the field holds a range, using google sheets we were able to ascertain the format in the field to be: {"start":"2023-04-30","end":"2023-04-30"} which we were able to store using Json.

The problem with the field needing to both a start and enddate means its hard to manipulate the field with automations or using exported.

Any way for us to add a feature request to have a date-range field and a date field? or, the current field being able to also accept a single date

[Rohan Swami]

Hi @Stas Hagemans , while we don't officially support JPD date fields in Automation, some users have been able to get their use cases working. This might be helpful to you: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Set-project-target-interval/qaq-p/2356633

[Stas Hagemans]

Hi Rohan, 

Thanks for the feedback, i looked at the solution and will see if it works. Having said that: It would be awesome if we would get the feature in the future. Dates are so critical to work with in workflows.