On this page
Field configuration
Before starting the field configuration, please follow the instructions for creating custom fields: Create a Custom Field
Step 1: Set a name and description
Provide a good name for the new custom field. Make it descriptive, concise, and easy to understand for others who will use it. Avoid using ambiguous or overly technical terms.
Step 2: Setup color and size
Set a color for the field and set different colors for your value.
Step 3 (optional): Set dependent due date
Select an issue's date field that serves as the due date representation.
Field view and edit
The time range is displayed in days (d), hours (h) and minutes (min). A negative value indicates that the task is overdue based on the configured due date.
Related Use Cases
More use cases are coming soon. In the meantime, check out our other use cases.
Jira Service Management (JSM)
For the “dependent due date” setting:
It is essential to populate or update the field initially through loading the issue view of the request, typically performed by an agent. Failure to do so will result in these fields remaining empty and consequently not displayed on the request view.
Before you can add a custom field for Jira Service Management (JSM) projects, you first need to setup the custom field
https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/edit-v2/47218689#Field-configuration
Then follow this guide to use the field in the request form or the portal view
JQL expression
The Due Date Countdown field can be accessed like this.
${fieldName}.Time left: number
${fieldName}.Due Date: date
Find further information here https://support.atlassian.com/jira-software-cloud/docs/find-specific-issues/
Example: perform a search for all issues with a due date set within the next 10 days (= 864,000,000 milli seconds).
"Due date countdown.Time left" < 864000000
Second Example: perform a search for all issues with a due date set to more than the current week in the future.
"Due date countdown.Due Date" > endOfWeek()
Data Structure (Automation)
To ensure accurate calculations, it's essential to set both the impact and urgency values when configuring the priority. Failure to do so may result in inadvertent overwriting of value during recalculation processes.
To set the value via automation, you need to at least set the dueDate value. timeLeft and formattedTimeRange are set on the next rendering step in the issue view
{
"dueDate": Date,
"timeLeft": number,
"formattedTimeRange": string
}
Example: assume today is the 14th December 2023, the dueDate is the 24th December 2023.
timeLeft is the difference from those two dates in milliseconds, the formattedTimeRange is a formatted representation of that range.
{
"dueDate": "2023-12-24T10:38+0100",
"timeLeft": 863952646,
"formattedTimeRange": "09d 23h 59min"
}