Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.0, 4.0.1, 6.2.4, 7.5.0
-
System Date Thursday, 17 Dec 2009
System Time 06:29:45 -0800
Current Working Directory C:\Upgrade_Nav\jira40\bin
Java Version 1.6.0_12
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 11.2-b01
Java Runtime Java(TM) SE Runtime Environment
Java VM Java HotSpot(TM) 64-Bit Server VM
User Name zira
User Timezone America/Los_Angeles
User Locale English (United States)
System Encoding Cp1252
Operating System Windows 2003 5.2
OS Architecture amd64
Application Server Container Apache Tomcat/5.5.28
Database type mysql
Database JNDI address java:comp/env/jdbc/JiraDS
Database URL jdbc:mysql://localhost/jiradb40?autoReconnect=true&useUnicode=true&characterEncoding=UTF8
Database version 5.0.51a-community-nt-log
Database driver MySQL-AB JDBC Driver mysql-connector-java-5.1.10 ( Revision: ${svn.Revision} )
External user management OFF
Crowd integration OFF
JVM Input Arguments -XX:MaxPermSize=256m -Xms3000m -Xmx5000m -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Datlassian.mail.senddisabled=false -Datlassian.mail.fetchdisabled=false -Datlassian.mail.popdisabled=false -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=C:\Upgrade_Nav\jira40\conf\logging.properties -Djava.endorsed.dirs=C:\Upgrade_Nav\jira40\common\endorsed -Dcatalina.base=C:\Upgrade_Nav\jira40 -Dcatalina.home=C:\Upgrade_Nav\jira40 -Djava.io.tmpdir=C:\Upgrade_Nav\jira40\temp
Modified Files [Installation Type: Standalone] templates/email/html/issuecommentedited.vm, templates/email/text/issuecommentedited.vm, templates/email/html/issuecommented.vm, templates/email/html/issueassigned.vm, templates/email/html/issueworkstarted.vm, templates/email/html/issueworklogged.vm, jira-application.properties, templates/email/html/issueupdated.vm, templates/email/text/issuecommented.vm, templates/email/text/jirasupportrequest.vm, templates/email/html/issueclosed.vm, templates/email/html/filtersubscription.vm, templates/email/text/filtersubscription.vm, WEB-INF/web.xml, email-template-id-mappings.xml, templates/email/html/issueresolved.vm, entityengine.xml, templates/email/html/issuemoved.vm, templates/email/text/errorinhandler.vm, templates/email/html/includes/summary-topleft.vm, log4j.properties, templates/email/html/issuereopened.vm, templates/email/html/includes/summary-bottom.vm, templates/email/text/usersignup.vm, templates/email/text/issueworklogged.vm, templates/email/html/issuedeleted.vm, templates/email/html/issueworkstopped.vm, templates/email/html/issuegenericevent.vm, templates/email/text/issueassigned.vm, templates/email/html/includes/footer.vm, templates/email/html/includes/header.vmSystem Date Thursday, 17 Dec 2009 System Time 06:29:45 -0800 Current Working Directory C:\Upgrade_Nav\jira40\bin Java Version 1.6.0_12 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 11.2-b01 Java Runtime Java(TM) SE Runtime Environment Java VM Java HotSpot(TM) 64-Bit Server VM User Name zira User Timezone America/Los_Angeles User Locale English (United States) System Encoding Cp1252 Operating System Windows 2003 5.2 OS Architecture amd64 Application Server Container Apache Tomcat/5.5.28 Database type mysql Database JNDI address java:comp/env/jdbc/JiraDS Database URL jdbc:mysql://localhost/jiradb40?autoReconnect=true&useUnicode=true&characterEncoding=UTF8 Database version 5.0.51a-community-nt-log Database driver MySQL-AB JDBC Driver mysql-connector-java-5.1.10 ( Revision: ${svn.Revision} ) External user management OFF Crowd integration OFF JVM Input Arguments -XX:MaxPermSize=256m -Xms3000m -Xmx5000m -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Datlassian.mail.senddisabled=false -Datlassian.mail.fetchdisabled=false -Datlassian.mail.popdisabled=false -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=C:\Upgrade_Nav\jira40\conf\logging.properties -Djava.endorsed.dirs=C:\Upgrade_Nav\jira40\common\endorsed -Dcatalina.base=C:\Upgrade_Nav\jira40 -Dcatalina.home=C:\Upgrade_Nav\jira40 -Djava.io.tmpdir=C:\Upgrade_Nav\jira40\temp Modified Files [Installation Type: Standalone] templates/email/html/issuecommentedited.vm, templates/email/text/issuecommentedited.vm, templates/email/html/issuecommented.vm, templates/email/html/issueassigned.vm, templates/email/html/issueworkstarted.vm, templates/email/html/issueworklogged.vm, jira-application.properties, templates/email/html/issueupdated.vm, templates/email/text/issuecommented.vm, templates/email/text/jirasupportrequest.vm, templates/email/html/issueclosed.vm, templates/email/html/filtersubscription.vm, templates/email/text/filtersubscription.vm, WEB-INF/web.xml, email-template-id-mappings.xml, templates/email/html/issueresolved.vm, entityengine.xml, templates/email/html/issuemoved.vm, templates/email/text/errorinhandler.vm, templates/email/html/includes/summary-topleft.vm, log4j.properties, templates/email/html/issuereopened.vm, templates/email/html/includes/summary-bottom.vm, templates/email/text/usersignup.vm, templates/email/text/issueworklogged.vm, templates/email/html/issuedeleted.vm, templates/email/html/issueworkstopped.vm, templates/email/html/issuegenericevent.vm, templates/email/text/issueassigned.vm, templates/email/html/includes/footer.vm, templates/email/html/includes/header.vm
-
4
-
6
-
Severity 3 - Minor
-
1
-
Description
The date picker allows you to choose a date like 2040 but by default this will be set as a date with a two digit year which causes it to be interpreted as 1940 as per the century selection algorithm for two digit years in Java's SimpleDateFormat.
Problem Description:
Client Due Date: 31-Dec-1940
Expected Completion Date: 16-Dec-1932
Both were set to 20XX not 19XX
This is related to a Java date bug.
From Atlassian support from ticket JSP-49395:
Weird, but I also came across that this is in the design. Java just assumes that if you are using 2 digits for the date it falls somewhere between 80 years before and 20 years after the date it was created.
For parsing with the abbreviated year pattern ("y" or "yy"), SimpleDateFormat must interpret the abbreviated year relative to some century. It does this by adjusting dates to be within 80 years before and 20 years after the time the SimpleDateFormat instance is created. For example, using a pattern of "MM/dd/yy" and a SimpleDateFormat instance created on Jan 1, 1997, the string "01/11/12" would be interpreted as Jan 11, 2012 while the string "05/04/64" would be interpreted as May 4, 1964.
http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html
Attachments
Issue Links
- is related to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
JRASERVER-71491 Jira should store all dates that contain years with 4 digits of precision, and not just 2 digits
- Gathering Interest
