Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Options to have DueDate use & show Date AND Time?

llagos
Contributor
September 21, 2018

Hello Jira users & experts.

I've read several threads about DueDate being a date-only field. Understood. But our customer wants to have Time as well as they have some business cases that justify it. Understood as well.

So, the options given by our Jira dev team are basically two:

#1 Use a temporal field in the UI instead (DueDateTmp) and the copy its value into DueDate.

#2 Not use DueDate at all, but just a new custom field (DueDateTime) everywhere

I'd like to get your feedback on:

- Are those 2 options "valid" (I'm not certain about #1; not sure DueDate is a "datetime" field at db-level)

- Are there any other options You may be aware of?

- pros and cons You may see with those options?

I'm worried about:

#1 - not showing the time in the UI, even if the can store it

#1 - default system behavior (SLA, notifications, etc.) just ignoring the time of DueDate

#2 - losing default functionality on dashboards, boards, SLA, notifications, etc.

I'd really appreciate your valuable knowledge on this one.

Thanks in advance,

1 answer

1 accepted

1 vote
Answer accepted
AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 24, 2018

Hi there.

I'll do my best to share my thoughts on the proposed solutions from your JIRA dev team:

#1 

The usage of a temporal custom field Date Time Picker (for example) to store the value and copy it to the Due Date field might not work since it stores the value of date and time while due date is specific to date only.

You might want to check on the Scripted field via Script Runner that can possibly grab the specific value of the date from the date time and copy it back to the due date field. I have not personally tried it before but it might be possible

#2

The default dashboards, Agile boards, features uses the default due date field. So, the functionality will be lost unless you are ready to revamp the rest of the functionality backend which will take up a lot of effort (I can't even tell if it is possible). 

In this case, option #1 will be a possible workaround if you are willing to spend some effort understanding how the scripted field works, if you ask me. 

llagos
Contributor
September 25, 2018

Thanks Ahmad...

We are buying ScriptRunner, so we'll take a look into it :)

Best regards!

AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 25, 2018

Hello again.

You are most welcome. Any time!

Meanwhile, please let me know how it goes on your end and share your experience using ScriptRunner to achieve this. Thanks!

Suggest an answer

Log in or Sign up to answer