Due Date extension

[John Peterson]

I have the following situation. The "Due Date" field doesn't contain time information. This causes wrong SLA (Time To Resolve) calculation for resolved incidents

Due: 29/Mar/18
Created: Thu 2018-03-29 08:37 GMT+0300
Updated: Mon 2018-04-02 23:08 GMT+0300
Resolved: Thu 2018-03-29 11:02 GMT+0300

Based on the date/time data ticket resolved according SLA - created at Thu 2018-03-29 08:37 and resolved in the same date in 3 hours, so ticket has to match SLA. But this ticket will be present in result of a query with statement: 
".. issueFunction in dateCompare("", "resolutiondate > duedate")" 
and this is wrong. 
Looks like the root cause of the issue is missing time data and JQL statement interprets the due date field value in following way:
29/Mar/18 00:00 and comparison based on the statement provided above will return True.

How to extend Due Date field?

[Nic Brough -Adaptavist-]

The due date is a field from Jira 1 that is intended to capture a deadline for development items.  It doesn't have a time because that sort of planning is done in weeks or months, not hours (and with no time element, all date fields assume midnight if asked about time)

Fixed dates are not really appropriate in service desk situations.  You don't usually set dates and times, you derive them from service level agreement rules.  If you do decide to put dates and times in, use a custom field for it, not due date.

[Amy Niebel]

I'm curious about how to get this feature added too. Our work does require a time. One of the great things about Jira is the ability to customize for various needs. If there's another work around for this, I'd be eager to know. We really need this.