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

Date calculations

tabdou

We created a custom field called "Due Date" vs. the system provided "Due date". I want to be able to create a filter that shows me all the tickets that are within 30 days based on the custom field "Due Date".

I know how to do that based on the "Due date" field using due = "30d" but I need it off the custom field.

Accepted answers

Bill Sheboy

Hi @tabdou -- Welcome to the Atlassian Community!

First thing, why did you create the field with such a similar name to the out-of-the-box field? I suspect that several things in Jira will have problems with that, such as automation rules.

Next, have you tried using the same syntax with your custom field as you did with the existing (or any other) date field?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @tabdou -- Welcome to the Atlassian Community!

First thing, why did you create the field with such a similar name to the out-of-the-box field? I suspect that several things in Jira will have problems with that, such as automation rules.

Next, have you tried using the same syntax with your custom field as you did with the existing (or any other) date field?

Kind regards,
Bill

tabdou

Excellent question Bill -- unfortunately, that field was created long before I arrived in my org.

Also unfortunately, it's not that clear to me (especially that I'm new to Jira). So I didn't really do any calculations when using the system provided "Date date". I found a solution online that literally says "due <= '30d'". Not sure where "due" comes from though as it seems to be a calculated field based on "Due date".

tabdou

But to your point, yes I am afraid that Jira might have an issue with fields being called same names with the exception of capitalization. My guess is that at some point, someone needed a Due Date field and didn't realize one already existed -- not sure!

Bill Sheboy

The built-in due date field is indeed a challenge as there are several names and capitalizations for it. "due", "Due", "duedate"... are a few of the names.

I recommend finding the custom field id for your replacement field and using that in the JQL, such as customfield_12345 <= 30d

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud