Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automations for date fields

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



1 answer

1 accepted

0 votes
Answer accepted
Rohan Swami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 15, 2023

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:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events