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

Custom Field "Date Time" is not following the format on the "Date/Time Formats"

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      The Date Time custom field does not comply to the rules of configuration of "Date/Time Formats" from the Look and Feel. Kindly refer to the attached screenshots.

      Example: Complete Date/Time Format dd/MMM/yy HH:mm

      Workaround prior to 4.4

      1. Shutdown JIRA instance
      2. Create the jira-config.properties in your JIRA Home Directory
      3. Insert the following into the file (example: dd/MMM/yy HH:mm) or other format that you want to have 
        jira.date.picker.javascript.format = %e/%b/%y
jira.date.time.picker.javascript.format = %e/%b/%y %H:%M
jira.date.time.picker.java.format = dd/MMM/yy HH:mm
jira.date.picker.java.format = dd/MMM/yy
      4. Delete the contents of JIRA Installation Directory\work directory
      5. Restart JIRA instance

      Workaround 4.4 and later

      1. Go to General Configuration > Advanced
      2. Configure the format as below 
        jira.date.picker.javascript.format=%e/%b/%y
jira.date.time.picker.javascript.format=%e/%b/%y %H:%M
jira.date.time.picker.java.format=dd/MMM/yy HH:mm
jira.date.picker.java.format=dd/MMM/yy

        1. date_format_1.JPG
          date_format_1.JPG
          39 kB
        2. date_format_2.JPG
          date_format_2.JPG
          87 kB

            [JRASERVER-29204] Custom Field "Date Time" is not following the format on the "Date/Time Formats"

            Lan Anh Nguyen added a comment - - edited

            Was this solved? because I still met the same problem.

            Lan Anh Nguyen added a comment - - edited Was this solved? because I still met the same problem.

            Kerrod Williams (Inactive) added a comment -

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Miguel De Dios added a comment -

            I applied the workaround for 4.4 or later (currently running 5.2.2)

            I noticed in the comments above that the structure mentioned was d.m.y and in the workaround it was e.b.y?

            Does this make a difference? Because right now I applied the workaround 4.4 or later and it hasn't changed my custom field date/time picker

            Also, would I need to reindex?

            Miguel De Dios added a comment - I applied the workaround for 4.4 or later (currently running 5.2.2) I noticed in the comments above that the structure mentioned was d.m.y and in the workaround it was e.b.y? Does this make a difference? Because right now I applied the workaround 4.4 or later and it hasn't changed my custom field date/time picker Also, would I need to reindex?

            Michael Knight added a comment -

            OnDemand customers do not have access to this screen. Please raise a support request if you need this changed.

            Michael Knight added a comment - OnDemand customers do not have access to this screen. Please raise a support request if you need this changed.

            Daniel Engdahl added a comment -

            Hello all,
            I'm at a loss here, is something missing (that is, probably something I totally overlooked) or is the purposed workaround (for 4.4 and later) not applicable to the OnDemand service of JIRA?

            Daniel Engdahl added a comment - Hello all, I'm at a loss here, is something missing (that is, probably something I totally overlooked) or is the purposed workaround (for 4.4 and later) not applicable to the OnDemand service of JIRA?

            Zul NS [Atlassian] added a comment -

            Great work in finding the settings Matthias! I have updated the workarounds accordingly.

            Zul NS [Atlassian] added a comment - Great work in finding the settings Matthias! I have updated the workarounds accordingly.

            Matthias Basler added a comment -

            Hi Eric and others.

            After today I am not sure anymore if this is a bug, a feature requrest or just a big misunderstanding caused ba a lack of documentation about what the different date/time settings in JIRA are supposed to affect.

            As I noted today in my support ticked, the four (newly discovered) settings
            jira.date.picker.java.format = d.mm.yy
            jira.date.picker.javascript.format = %e.%m.%y
            jira.date.time.picker.java.format = dd.MM.yy HH:mm
            jira.date.time.picker.javascript.format = %d.%m.%y %H:%M
            achieve the desired effect.

            The problem is that it is not obvious to a normal admin that these settings exists because they are hidden away in the "Extended settings" on a completely different location of the configuration than the mentioned date/time formats.
            Also it is unclear to me in what way these two sets of settings work together or interfer with each other. They seem somewhat redundant.

            So maybe the above mentioned date/time settings are not supposed to be applied to fields because there are separate settings for them?

            I propose to make the NLS configuration more obvious and in one place. Guess I should open a separate issue for this.

            P.S. The original workaround given is not sufficient, since the Java+JavaScript formats of each field type have to be in sync. Otherwise edit masks will reject the select date values of the date picker.

            Matthias Basler added a comment - Hi Eric and others. After today I am not sure anymore if this is a bug, a feature requrest or just a big misunderstanding caused ba a lack of documentation about what the different date/time settings in JIRA are supposed to affect. As I noted today in my support ticked, the four (newly discovered) settings jira.date.picker.java.format = d.mm.yy jira.date.picker.javascript.format = %e.%m.%y jira.date.time.picker.java.format = dd.MM.yy HH:mm jira.date.time.picker.javascript.format = %d.%m.%y %H:%M achieve the desired effect. The problem is that it is not obvious to a normal admin that these settings exists because they are hidden away in the "Extended settings" on a completely different location of the configuration than the mentioned date/time formats. Also it is unclear to me in what way these two sets of settings work together or interfer with each other. They seem somewhat redundant. So maybe the above mentioned date/time settings are not supposed to be applied to fields because there are separate settings for them? I propose to make the NLS configuration more obvious and in one place. Guess I should open a separate issue for this. P.S. The original workaround given is not sufficient, since the Java+JavaScript formats of each field type have to be in sync. Otherwise edit masks will reject the select date values of the date picker.

            Eric Dalgliesh added a comment -

            I know this seems like a bug, but it's actually an improvement request to have the date/time format applied to custom fields.

            Eric Dalgliesh added a comment - I know this seems like a bug, but it's actually an improvement request to have the date/time format applied to custom fields.

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: