Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-11966

Enhanced Reports - Custom date fields within enhanced reports compel a user to use d/MMM/yy validation scheme

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None

      NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding bug report.

      Customer is attempting to modify date format of date pickers in accordance with documentation located on an Atlassian Documentation site tailored to Customizing the Look and Feel.

      All Customer functions have been replicated in a test environment using Ubuntu Linux 14.04 VM, JIRA Server 6.3.15. Customer navigates to Administration > General Configuration > Advanced Settings. Next, the customer changes the default value of jira.date.picker.javascript.format and jira.date.picker.java.format (exhibit A). Updates occur without incident.

      Meanwhile, from the Agile menu, customer specifies a Kanban Board ("KanBoardAcme"). Under "Try the enhanced reports in JIRA Agile Lab", customer elects the "Enable" button (exhibit B). Scroll to the bottom of that page, and see the TimeScale area fail validation. Please see (exhibit C).

      When the Advanced Setting sets these values, they are global, are they not? Therefore, the date-picker should use those settings to enforce its validation rules.

        1. exhibit A.png
          exhibit A.png
          265 kB
        2. exhibit B.png
          exhibit B.png
          102 kB
        3. exhibit C.png
          exhibit C.png
          172 kB

              Unassigned Unassigned
              selahi Shafinaz Elahi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: