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. 

[Gabriela · Accepted solution]

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

{{now.diff(issue.created).abs.days}}

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.

[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. 

[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

[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:

Disclosure: I work on the team behind JXL.

Best, Paul