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

Formula Field Question

Mikel Whipple

Using the new formula field I want to create an aging field. It seems it can calculate between two fields but I am just trying to get it to calculate how many days since created. I have tried, {{Created.diff(now).days.plus(1)}} but it does not like it. Looking at the supported functions it does not seem doable but wanted to check in case I am missing something.

Accepted answers

Gabriela - LeanZero

Hi @Mikel Whipple, you're not missing a function. The native formula field can't produce a days-since-created / aging value at all, so this isn't a syntax you can fix.

`{{Created.diff(now).days.plus(1)}}` is Automation smart-value syntax; the formula field uses function calls like `DAY_DIFF(date1, date2)`, so it was never going to parse. The real blocker is that formula fields have no NOW() or TODAY() (or any current-date) function, which you can confirm in the supported-functions list (https://support.atlassian.com/jira-cloud-administration/docs/supported-functions-for-formulas/). DAY_DIFF only measures between two dates already stored on the work item, and the field doesn't recompute against today, so there's nothing to diff Created against.

The native way to get an aging field is Automation. Use a scheduled rule (say daily) with an Edit issue action that sets a Number field to

Wrap it as {{#=}}{{now.diff(issue.created).abs.days}} + 1{{/}} if you want the creation day counted. It only refreshes when the rule runs, so on a daily schedule it can lag up to a day; a Marketplace calculated-field app recomputes live on view if you need it always current.

All comments

Gabriela - LeanZero

Hi @Mikel Whipple, you're not missing a function. The native formula field can't produce a days-since-created / aging value at all, so this isn't a syntax you can fix.

The native way to get an aging field is Automation. Use a scheduled rule (say daily) with an Edit issue action that sets a Number field to

zoltanersek _outpostlabs_dev_

Exactly, there is no dynamic now() function, so calculating a continuously updating filed isn't supported yet

Mikel Whipple

Thanks for the reply. That is what I thought, we have tried using the automation but we get throttled due to the number of issues that need it. This is why Jira is our favorite 4 letter word. They roll out functionality but it doesn't really meet the need.

Paul Glantschnig _Appfire_

Hi @Mikel Whipple,

You mentioned the automation route gets throttled at your issue volume. That's the usual dead end with aging fields: the value changes daily on every open issue, so any rule that writes it back has to touch all of them.

If an app from the Atlassian Marketplace is an option for you, JXL for Jira sidesteps that entirely. It calculates the value live in the view instead of storing it on the issue, so there's no rule to run and nothing to throttle, no matter how many issues need it. There's a ready-made "Time since created" column, and if you want your exact day count it's a one-line formula: DATEDIF(this.createdDate, NOW(), "D") + 1. You can sort, filter, and group by the result like any other column.

This is how it looks in action:

Time since created column in JXL

Disclosure: I work on the team behind JXL.

Best, Paul

Mikel Whipple

Hello. Working with Atlassian support there is a also a 250 character limit, so we opened this to increase that.

https://jira.atlassian.com/browse/JRACLOUD-98844

Monika Ambrozowicz_Seibert_

Hi @Mikel Whipple, the native formula field in Jira Cloud does support some date calculations, but the pattern you need isn't currently available - it is limited to calculations between two existing field values, not between a field and the current timestamp. So you're not missing anything; what you're trying to do just isn't supported natively yet.

If you're open to a Marketplace app, Awesome Custom Fields has an Advanced Formula field type that does support date-to-now calculations, including exactly the kind of aging field you're describing - calculating how many days have elapsed since an issue was created. Full disclosure: I'm working with the team behind the app but it also means I've seen a lot of use cases, where fields from Awesome Custom Fields filled the gaps in native Jira.

You can check the app's documentation for formula syntax examples or try it for yourself for free.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud