Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-36387

Date/Time picker JavaScript format for jira.date.time.picker.java.format is incorrect

      Summary

      The JavaScript format does not match the Java format for jira.date.time.picker.java.format as below:

              <property>
                  <key>jira.date.time.picker.java.format</key>
                  <name>DateTime Picker Format (Java)</name>
                  <description>This part is only for the Java (server side) generated datetimes. Note that this should correspond to the javascript datetime picker format (jira.date.time.picker.javascript.format) setting.</description>
                  <descriptionKey>jira.date.time.picker.java.format.desc</descriptionKey>
                  <default-value>dd/MMM/yy h:mm a</default-value>
                  <type>string</type>
                  <validator>com.atlassian.validation.SimpleDateFormatValidator</validator>
                  <admin-editable>false</admin-editable>
                  <sysadmin-editable>true</sysadmin-editable>
                  <requires-restart>false</requires-restart>
              </property>
              <property>
                  <key>jira.date.time.picker.javascript.format</key>
                  <name>DateTime Picker Format (JavaScript)</name>
                  <description>This part is only for the JavaScript (client side) generated date times. Note that this should correspond to the java datetime picker format (jira.date.time.picker.java.format) setting.</description>
                  <descriptionKey>jira.date.time.picker.javascript.format.desc</descriptionKey>
                  <default-value>%e/%b/%y %I:%M %p</default-value>
                  <type>string</type>
                  <admin-editable>false</admin-editable>
                  <sysadmin-editable>true</sysadmin-editable>
                  <requires-restart>false</requires-restart>
              </property>
      

      Expected Behaviour

      Either the Java format should be dd/MMM/yy hh:mm a or the JavaScript format should be %e/%b/%y %l:%M %p

      It looks like it is set to %I instead of %l perhaps as an accident as they can look identical depending upon the font used?

      $ date +'%e/%b/%y %I:%M %p'
       7/Jan/14 05:51 pm
      $ date +'%e/%b/%y %l:%M %p'
       7/Jan/14  5:51 pm
      

      Actual Behaviour

      See the file excerpt above.

      Replication Steps

      This is in JIRA 6.1.5 jpm.xml, reviewing the file for that version shows the error.

      Notes

      This behaviour is explained in more detail in Changing the Due Date Input Format.

            [JRASERVER-36387] Date/Time picker JavaScript format for jira.date.time.picker.java.format is incorrect

            Atlassian Update - 14 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 14 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Data Center

            Dave C added a comment -

            Yes ohernandez@atlassian.com that looks the only thing that is required.

            Dave C added a comment - Yes ohernandez@atlassian.com that looks the only thing that is required.

            dcurrie@atlassian.com Is this just a matter of correcting the default value for the JavaScript format in jpm.xml ?

            Oswaldo Hernandez (Inactive) added a comment - dcurrie@atlassian.com Is this just a matter of correcting the default value for the JavaScript format in jpm.xml ?

              Unassigned Unassigned
              dcurrie@atlassian.com Dave C
              Affected customers:
              3 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: