Luc, your IT Team is awesome! Thanks! It works perfectly! We use JIRA 4.4.5.

One note for other folks who may implement this:
I came across a problem in IE 9 whereby the calendar gadget was not appearing. When I would click on the calendar icon the screen would jump back to the top, but no calendar would appear. I played around with the compatibility settings in IE and that got the calendar to pop up, but honestly, when I put the compatibility settings back to their original settings, the calendar continued to display properly. If you encounter this problem, I suggest going down this route first:
Administration -> System, Look & Feel.
Scroll to the bottom of the page where you will see "Refresh Client Resources". Click on that.
Click on "Clicking this link".

Here is the workaround of my IT team.

You have to modify the file Calendar-min.js located /includes/lib/calendar/

This file looks like there is no line break so I can't give the line but you have to include this code between :

...
this.isPopup=false
}
// start code to add
if (this.dateStr) {
       var dateStrCustom = ""+this.dateStr;
       dateStrCustom = dateStrCustom.replace(/-/g,"/").replace(/(\d\d)+T+(\d\d)/, "$1 $2");
        this.date=new Date(dateStrCustom);
}

if (!this.date || isNaN(this.date)) {
        this.date=new Date();
}
// end code to add

var table=Calendar.createElement("table");
...

It works with IE9 and FF8, our JIRA version is 4.4.3.

Has anyone found a workaround for this problem? We can't simply upgrade to JIRA 6.

Thanks for the information. We were going to upgrade JIRA after June 15. We might just wait 10 more days then if the dates for 6.0.3 doesn't change.

6.0.3 is currently scheduled to be public on the 25th June. Whether to wait or not depends on how important this is for you.

Thanks for the information, Eric. It looks like it'll be fixed in version 6.0.3. We were planing to upgrade our Production instance of JIRA to 6.0.1 next week. If 6.0.3 will be released soon, should we wait until then as this issue is most likely to be addressed in that version?

This issue is in progress, but it's turning out to be much thornier than we had anticipated. We don't have a definite date as yet.

Any updates when this will be fixed now that JIRA 6.0 is released??

Thanks
Ahdip

Hi,
We are experiencing this problem and the custom date time fields are configured for us to use in conjunction with VertygoSLA plug-in.
For us this is much higher than a 'Minor' priority becuase the dates are used to set the SLA due dates (often a matter of hours) which have a financial penalty associated with them. Whilst we can tell users to be careful when setting the date time fields, this is a manual workaround and if errors happen we as an organisation could lose credibility with our clients.
Please can you give an indication of when this issue may be resolved.
Regards
Michelle

Hi apokharel@fncinc.com and lucgauf,

Thanks for your feedback. Priority is only one of the inputs into what order we should fix bugs. Interaction like this is another. Addtionally there are currently four customers with comments on this issue and 6 votes. Those are not insignificant numbers (though they also are certainly not the highest), and you obviously still care about this bug, so I'm going to add it to the backlog.

If you're after timelines, there are just over 200 other issues on that shorter term backlog at the moment so this is unlikely to get fixed before 6.0 is released, making the most likely schedule for this at some stage in the 6.0.x lifecycle. We don't usually give estimates of when things will be fixed because they turn out to be wildly inaccurate most of the time, so please bear that in mind when considering this.

Regards,
Eric