Ever find yourself wondering about the time left to complete a task or needing a simple way to assess the urgency of your assignments?
Whether it's selecting a date from a calendar, manually setting a date, or linking to other due dates, you can set the due date as per your preference. The Due date field dynamically updates whenever you view or update the issue. It calculates and displays the difference between the current date and the due date right at your fingertips. The field is presented using SVG number fields, ensuring a straightforward and user-friendly representation of the remaining time.
Field configuration
Before starting the field configuration, please follow the instructions for creating custom fields
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
WSJF (Weighted Shortest Job First)Calendar fieldJira Service Management (JSM)
The Time in status field is currently not available for Jira Service Management.
JQL expression
The Due Date Countdown field can be accessed like this.
${fieldName}.Time left: number
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
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"
}