Due dates don't have a time element, they're just a date. So I'm afraid there's nothing you can do.
Ok, not the answer I was looking for but it is what it is.
If this is the case (which it is) then it would be nice that watcher email that is created when a new issue is created did not include a fixed time of 12:00 on the date fiels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I think that you have changed the format of dates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That won't help, as due date is a date only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But, i think that it can add a custom field date time type and set it with the value of the due date with time
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough,
yes it's right what do you say, due date is date type and not date time type.
I paid no attention.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Of course you can add a custom field. But then it's not the due date.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
so are you satying JIRA forgot to add the most important feature and never cared to add it after looking at the forums of people getting mad at it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is really bogus explanation. I want to bring Service organization that depends on delivering at specified time, so I have to create workaround with some custom field and still explain to people why the should Jira and not other systems that already care for it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's not a bogus explanation. It's an explanation of how it is.
Not why.
I would guess that the why is because most people don't consider time when talking about due dates for things. How often do you hear "that will be done by 3:15 next Tuesday" as opposed to "that will be done by Tuesday"? It's very rare to hear a time something should be due, so the system field doesn't bother.
Due date is also not something I would use in a service organisation, I'd be looking at using SLAs and queues to handle when something needs doing by.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.