Currently, Formula type custom fields in Jira Cloud do not support dynamic date/time functions such as now() or today(). This limits the ability to create calculated fields that reference the current date or time — a common requirement for tracking SLA adherence, aging of issues, days since last update, or time remaining until a due date.

Use Case

As a Jira administrator, I want to use functions like now() or today() within Formula custom fields so that I can:

• Calculate the number of days an issue has been open (e.g., now() - created)

• Determine days until a due date (e.g., dueDate - today())

• Flag issues that have been idle for more than X days (e.g., now() - lastUpdated > 7)

• Build dynamic dashboards and filters based on real-time calculated values without relying on automation workarounds or third-party apps

Current Workarounds

• Using Automation rules to periodically stamp a "last calculated" date into a separate field — this is resource-intensive and not real-time.

• Relying on third-party marketplace apps (e.g., ScriptRunner, Power Custom Fields) which add cost and maintenance overhead.

• Manually updating fields, which is error-prone and doesn't scale.

Expected Behaviour

Formula custom fields should support at minimum:

• now() — returns the current date and time

• today() — returns the current date (without time component)

• Date arithmetic — e.g., now() - {created} returning a duration or number of days

Impact

This would significantly enhance native reporting and filtering capabilities, reduce dependency on third-party apps, and align Jira Cloud's formula fields with what users expect from a modern calculation engine.