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

Invalid format error when building and releasing a version

XMLWordPrintable

    • 9.07
    • 84
    • Severity 3 - Minor
    • 535
    • Hide
      Atlassian Update – 11 June 2024

      Dear Customers,
      Thank you for reporting this issue. In the last weeks we have been working on fixing it.

      Summary of the problem:

      The problem stemmed from the recent modification made for JRASERVER-41646. The issue came to light when it was discovered that the scheduled job responsible for releasing the version was internally utilizing an invalid data format.

      New behaviour after the change:

      Moving forward, the internal job will now schedule new 'Release' and 'Build and Release' jobs using the correct data format. This adjustment ensures that any newly triggered operations should be completed successfully.

      In cases where unfinished jobs were triggered by 'Build and Release' with an invalid data format before the upgrade to the fixed version, they may still be in progress. To address this issue, simply trigger the 'Release' operation once more.

      Best regards
      Daniel Dudziak
      Principal Software Engineer

      Show
      Atlassian Update – 11 June 2024 Dear Customers, Thank you for reporting this issue. In the last weeks we have been working on fixing it. Summary of the problem: The problem stemmed from the recent modification made for JRASERVER-41646 . The issue came to light when it was discovered that the scheduled job responsible for releasing the version was internally utilizing an invalid data format. New behaviour after the change: Moving forward, the internal job will now schedule new 'Release' and 'Build and Release' jobs using the correct data format. This adjustment ensures that any newly triggered operations should be completed successfully. In cases where unfinished jobs were triggered by 'Build and Release' with an invalid data format before the upgrade to the fixed version, they may still be in progress . To address this issue, simply trigger the ' Release ' operation once more. Best regards Daniel Dudziak Principal Software Engineer

      Issue Summary

      The error "Invalid format" is shown in the atlassian-jira.log when building and releasing versions.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. In JIRA Admin > System > Look and Feel set the Day/Month/Year Format to a format using spaces, e.g. 'dd.MMM.yy' (or any other date time format that is not the default)
      2. Go to the Versions list of any projects, and click Release for a Version; You will see it released without problems
      3. Then click Unrelease for the same version
      4. Now click Build and Release, and the screen refreshes multiple times falling into a loop.
      5. Return to the Versions lists and you will see the Version still is unreleased

      Expected Results

      The Version should be released regardless of the format configured in Look and Feel

      Actual Results

      The Version remains Unreleased and the Version page enters into a loop.

      The below example exception is thrown in the atlassian-jira.log file:

      http-nio-8080-exec-XXX url: /jira/rest/bamboo/1.0/status/10002/SCRUM-SP-X; user: USER ERROR USER XXXXX SESSIONID IP_ORIG /rest/bamboo/1.0/status/10002/SCRUM-SP-5 [c.a.j.p.e.bamboo.service.BambooReleaseServiceImpl] Unexpected Error Has Occured Performing Release
      java.lang.IllegalArgumentException: Invalid format: "14.Jun.23" is malformed at ".Jun.23"
      	at org.joda.time.format.DateTimeFormatter.parseLocalDateTime(DateTimeFormatter.java:900)
      	at com.atlassian.jira.datetime.JodaDateTimeFormatter.parse(JodaDateTimeFormatter.java:42)
      	at com.atlassian.jira.datetime.DateTimeDatePickerFormatter.parse(DateTimeDatePickerFormatter.java:28)
      	at com.atlassian.jira.datetime.DateTimeFormatterImpl.parse(DateTimeFormatterImpl.java:51)
      	at com.atlassian.jira.util.DateFieldFormatImpl.parseDatePicker(DateFieldFormatImpl.java:42)
      	at jdk.internal.reflect.GeneratedMethodAccessor1139.invoke(Unknown Source)
      	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.base/java.lang.reflect.Method.invoke(Method.java:566)

      Workaround

      1. Go to JIRA Admin > System > Look and Feel
      2. Revert the Day/Month/Year Format to the default format settings: dd/MMM/yy

      Or, release the version manually from the project's administration page for version.

      Notes

      There seem to be correlation with the Jira Admin > System > General Configuration > Advanced Settings > jira.date.picker.java.format. If reverting the values in 'Look and Feel' doesn't work, check the jira.date.picker.java.format value and sync it with the value in 'Look and Feel'

            ddudziak Stasiu
            458e633c07a6 Jose Antonio Uribe
            Votes:
            85 Vote for this issue
            Watchers:
            117 Start watching this issue

              Created:
              Updated:
              Resolved: